what if for example you want to hard code a hash salt into your code?..... if the code is readable, then so is the salt. I would vote for unreadable code 100% of the time.
On Wed, Jun 6, 2018 at 10:38 AM, Brian Milby via use-livecode < use-livecode@lists.runrev.com> wrote: > For commercial I would think so, but don’t see any issue on the community > side. > On Jun 6, 2018, 9:34 AM -0500, Bob Sneidar via use-livecode < > use-livecode@lists.runrev.com>, wrote: > > Don't we want that NOT to be possible?? Otherwise bring back the runtime > engine and run the app as a stack file of the runtime. > > > > Bob S > > > > > > > On Jun 5, 2018, at 19:37 , Brian Milby via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > > > > Looking at the code, “deflate” is called on the stack as it is being > written out (zlib). So while not easy, it should be possible to separate a > stack file from the binary if deployed from the community edition. It would > take a bit of work to figure out where the file started and ended. Well > over what I would be willing to tackle at the moment. For anyone so > motivated, the relevant source code is in deploy*.cpp (along with the > header files). > > > > _______________________________________________ > > use-livecode mailing list > > use-livecode@lists.runrev.com > > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
