1. shrouding
Has anyone ever tried to shroud anything large lib. like win32lib.ew
The first problem is that you use any global constants in your program
some names will be changed and some will not be so the user of lib. will
not be able to use the constants in his program.
If you want to use a 1, 2, 3 letter name for a function then the
shrouder will change the names to what it wants to because it uses
the names a=1 b=22 c=223 through a cycling alphabet to create shrouded
names. It seems to me the shrouder should you internal names that
contain a invalid character prefix so they would never conflict with a
user's name ( because the user could not use the invalid name prefix
externally }.
I tried shrouding a working lib of my own and also david's win32lib and
neither worked after shrouding without errors.
I guess you can only use the shrouder in binding because it isn't
of any use unless you want to write your programs the way the shrouder
wants them written or use simple includes that aren't worth shrouding.
The shourder should be able to shroud any working include or lib
and make it capable of use as though it was not even shrouded without
any modification of the authors code.
Bernie
2. Re: shrouding
Bernie Ryan wrote:
> Has anyone ever tried to shroud
> anything large lib. like win32lib.ew
I've written a utility called 'fix' that's included with Win32Lib. It does a
lot of what shroud does, but it handles routine_id correctly. The catch is
that it shrouds *everything*. You could probably rewrite it to pay attention
to global tokens, and not shroud those.
-- David Cuny
3. Re: shrouding
Thanks David
I would think that shroud should work as advertized without
writing my own shrouder or rewriting my code.
Bernie
