Good to know its fast, but I guess my concern is that a "try" statement would slow down each line of a script, and so the speed hit would be a factor of how long the script was.
Not sure why, but I always assumed it would work a bit like debugging or using the "do" statement and significantly slow things down, so I've not used it to wrap long complex scripts. 2008/7/27 Mark Schonewille <[EMAIL PROTECTED]>: > Hi David, > > I am using the try control structure in a plugin, which sometimes runs tens > or hundreds of times per second, and I haven't experienced any noticeable > speed issues. > > -- > Best regards, > > Mark Schonewille > > Economy-x-Talk Consulting and Software Engineering > http://economy-x-talk.com > http://www.salery.biz > > Benefit from our inexpensive hosting services. See > http://economy-x-talk.com/server.html for more info. > > > On 27 jul 2008, at 12:05, David Bovill wrote: > > Does anyone know what the speed implications of wrapping a long >> complicated >> script in a try statement is? I have an optional tidy routine that would >> be >> useful to use before exporting - but due to its nature there may be >> errors. >> Is there any need to be cautious in using "try" routines for performance >> issues, or is it in general harmeless and you can go around sprinkling >> them >> everywhere? >> > > _______________________________________________ > use-revolution mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution > _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
