> > Since a static variable is only accessible inside of its script
> > file, this would not work unless I added some new functions to go
> > "outside the language", eg
> > getstatictvar("scriptname", "staticvarname")
> > setstaticvar("scriptname", "staticvarname")> > Personally, I believe that you should not waste your time. > > If a script writer wants to access the static variable of another > script then s/he should program a subroutine that returns its value. > Yes, I agree that "getter/setter" routines are the cleanest. And if the base requirements is to be able to persist the static variables in a script, then my style would be to provide a [EMAIL PROTECTED] entry point to be called to due that (along with a [EMAIL PROTECTED] to unpersist). (BTW< I don't know why you would want to persist locals). But I can imagine someone saying that they would like a way to persist all statics only from routines which had actually been used during this PowerPro session. This could be done if I provided the above routines plus a version of allstatics which returned both the routine name and the variable name. But for now I don't plan to do it. ------------------------ Yahoo! Groups Sponsor --------------------~--> Yahoo! Domains - Claim yours for only $14.70 http://us.click.yahoo.com/Z1wmxD/DREIAA/yQLSAA/JV_rlB/TM --------------------------------------------------------------------~-> 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/
