[wx-dev] wxFileSelector functions compatibility (was: watcom template errors)

[Vaclav Slavik]

Hi,

Vadim Zeitlin wrote:
>  The trouble is that without default parameters in template
> functions we have no way (or, at least, no nearly reasonable way)
> to support passing NULL to wxFileSelector and related functions. 

To be precise, it's doable, but at the cost of adding 8 or so 
additional overloads.

> won't go into the details but supposing that I don't miss something 
> obvious, we can only drop support for using NULL in these functions
> -- people will get compilation error for the code doing this but
> will hopefully discover relatively quickly that they have to
> replace NULL with wxEmptyString. Do you think this would be
> acceptable?

Also note that this already had to be done in other places where NULL 
was accepted, so this is not the first place where this would happen.

Thanks,
Vaclav

-- 
PGP key: 0x465264C9, available from http://pgp.mit.edu/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.wxwidgets.org/pipermail/wx-dev/attachments/20070702/38a2a83c/attachment.pgp