Hiya (Nice to see all this discussion.)
Dossy Shiobara wrote:
While it would be easy to add the necessary code to clean up namespace variables, I think it isn't being done because doing it could get "expensive" because, in order to implement it, we'd have to iterate over every single namespace (which could be a large number) then retrieve the list of variables per namespace and unset them.
Certainly makes sense with the current architecture.
Avoid namespaces. :-)
Well, namespaces are very handy. I've used them in the past for both things that are meant to be "server level", and also in libraries that may get used at the "request level" in several scripts. The latter is particularly useful as you can happily use functions without worrying about poluting the caller's scope or doing messy things like passing variable names and upvar'ing. I'm certainly not in a position to rewrite all the code I've got that already uses namespaces. However, I'm pretty sure that a fair amount of it is re-use safe in that the API ensures the namespace variables are cleared/initialised appropriately on each invocation. Some code review will be required to confirm this, but I can probably live with that.
Jim's "singlescript" or whatever it was called will do what you want: the entire ADP gets turned into a single script, and an error anywhere in it will abort the entire script, naturally.
Yes, I mentioned that before as fulfilling the requirement (though doing a bit more which whilst not necessary for me, shouldn't hurt). Hence my question regarding a 4.1 release. PS: I plan to update the wiki in the next few days - I'll post here afterwards so people can correct my mistakes. :) Cheers -- Stuart Children -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
