--- In [email protected], [EMAIL PROTECTED] wrote: > > > > maybe this should be a plugin? > > > > > > please! It would help us scripters move towards a shared > > development framework... > > > > Umm... I did not mean to volunteer to write it... > > Couldn't you use existing file-writing techniques and just create it with a > script that is called externally to your current script?
Of course. But the original poster wanted to be able to leave all the log statements in his scripts and not use a bunch of if statements to decide whether to execute them. Assuming you don't want to write to log file all the time, you need something like [EMAIL PROTECTED](scriptname, text_to_log_) Then you need to have a separate startup routine or command which is [EMAIL PROTECTED](name,flag) which specifies whether the logging is done for routine called name. But someone might complain that it is inefficient to call a log script written in PowerPro script langauge just to immediately return if scripting is disabled for that routine. Hence the plugin suggestions. ------------------------ Yahoo! Groups Sponsor --------------------~--> Fair play? Video games influencing politics. Click and talk back! http://us.click.yahoo.com/T8sf5C/tzNLAA/TtwFAA/JV_rlB/TM --------------------------------------------------------------------~-> Attention: PowerPro's Web site has moved: http://www.ppro.org Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/power-pro/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
