If the Win32::GUI::Constant package is a XS/C code we'll be able to come
up with various algorithms that compress the text strings meaning the
resulting dll could be relatively small.
But that imports the name into the current package, which is true namespace
clutter, and using bare-name const
We wouldn't _need_ to change the algorithm, but if we do generate from
(say) a flat file of constants (or something more sophisticated, like the
Windows header files), the potential for using more constants in a program
is larger, and a better algorithm, while it won't change the run time of
th
I assume you would end up with something like:
use Win32::GUI::Constant qw (ES_WANTRETURN with a big list of other
constants that you want);
With the Constant package creating the passed list of constants in the
callers namespace? You could also have:
use Win32::GUI::Constant qw (all); #all
3 matches
Mail list logo
