1. shroud ?
- Posted by Bernie Ryan <xotron at localnet.com> Jul 13, 2001
- 396 views
I think this has been discussed before, but I've forgot the reason. When I shrouded some library code, I get a message that because routine_id I have to use clear. So I use the clear and shroud the code again. And then when I try to use the library I get error reports saying that constant CONSTANTNAME has not define. Also I have a include file (which is not shrouded) that contains the instance() built-in function and the interpeter says that the function is not defined. My code all works prior shrouding. I know Dave Cuny had some problem with shrouding windows programs. What is wrong and will this be fixed ver 2.3 Bernie
2. Re: shroud ?
- Posted by Robert Craig <rds at RapidEuphoria.com> Jul 15, 2001
- 407 views
Bernie Ryan writes: > ... Also I have a include file (which is not shrouded) that > contains the instance() built-in function and the > interpeter says that the function is not defined. I'm not sure about the other problems you mentioned, (lots of people bind and/or shroud Win32Lib-based programs) but instance() was introduced in Euphoria 2.1 (in misc.e). Be sure not to mix in files from Euphoria 2.0. Regards, Rob Craig Rapid Deployment Software http://www.RapidEuphoria.com
3. shroud ?
- Posted by Bernie Ryan <xotron at BUFFNET.NET> Apr 26, 2000
- 369 views
If a include file is shrouded and it contains constants. Then this file is included by a user how will the user be able to use those constants if the shroud program changes or renames the constant names ??
4. Re: shroud ?
- Posted by Brian Broker <bkb at CNW.COM> Apr 26, 2000
- 378 views
- Last edited Apr 27, 2000
On Wed, 26 Apr 2000 19:16:26 -0400, Bernie Ryan wrote: >If a include file is shrouded and it contains constants. > > Then this file is included by a user how will the user be able to > use those constants if the shroud program changes or renames > the constant names ?? According to the Reference Manual: "You can distribute a shrouded/scrambled .e include file that people can include in their programs without seeing your source code. Symbols declared as global in your main .e file will not be renamed, so your users can access routines and variables with meaningful long names, while the rest of your file remains shrouded." -- Brian