On 31/7/01 10:23 am, Nathan Reilly <[EMAIL PROTECTED]>
wrote:
> I've just been looking through a "compliled" application that was
> created for BSD (and Mac and Windows), and came across the source to
> my stack.
>
> If I was using clear text passwords for anything, or cared at all for
> the IP values of the code, this is not a good thing to find.
>
> What puzzles me, is that when I use the build option to encript, my
> stack disappears from strings(1)'s output.
>
> If this were a compiled script, I see no reason why the script would
> remain in the file when you build your distribution.
It is compiled, but only to a limited extent. You get the benefits of
single pass error checking and a massive performance advantage over
languages such as HyperCard and SuperCard. However, as such the scripts are
available in the final application (the virtual compiler works when an
object is loaded and is virtually instant). This gives you the advantage of
being able to run and edit all at once in the development environment, as
well as the ability to "do" text as if it were a script at run time. You
can encrypt your standalone during the build process so the scripts are not
accessible.
Regards,
Kevin
Kevin Miller <[EMAIL PROTECTED]> <http://www.runrev.com/>
Runtime Revolution Limited - Power to the Developer!
Tel: +44 (0)131 718 4333. Fax: +44 (0)1639 830 707.
