Hi, Usually, I open a stack in a text editor before opening it in LiveCode, if I don't know whether the originating source of the stack can be trusted. By looking at the scripts, I'm usually able to tell what the stack does.
-- Best regards, Mark Schonewille Economy-x-Talk Consulting and Software Engineering Homepage: http://economy-x-talk.com Twitter: http://twitter.com/xtalkprogrammer KvK: 50277553 New: Download the Installer Maker Plugin 1.6 for LiveCode here http://qery.us/ce On 12 mei 2011, at 16:05, Nonsanity wrote: > I also got this as a personal email and responded with some hints and tips, > but I didn't do the work for him/her for two reasons: 1) it DOES sound like > a school assignment, very much so. And 2) NEVER open attachments from people > you don't know, that you weren't expecting, or that seem suspicious in any > way. > > Remember, it's possible to write a really NASTY Livecode stack, or ANY > program for that matter. You take a risk whenever you launch an application. > Developer communities need a modicum of trust between them, but we still do > need to be careful. And report suspicious behavior... Offset the risk trust > brings with some crowd-sourced safety. :) > > Home my tips help you, JYST, and good luck on your assignment. We're here to > answer SPECIFIC questions you may have. :) > > ~ Chris Innanen > ~ Nonsanity _______________________________________________ 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
