Hi Charles, > Is this what you mean?
Yes and no. I like the idea of the library being a db listening on a port. But it should be only one of the possibilities. It might be just a script of functions - like a member of a block. Though the library structure could be hiearchical too if that is a better organisation of reusable things. So there is an addressing issue - how does one refer to the thing wanted. Then there is the execution model - when is the code included. I'd like to be able to build a script - the result being a script with no library references. I might do that when I'm rebuilding my website/rebsite for lots of scripts or I might want to do it on demand in response to a CGI request for the script with some parameterisation. Other possibilities abound. In summary, I guess my interest is in: (a) how to address reusable code snippets (b) how to compose the new script from reusable snippets and the specifics of the script wanted. (c) being able to do so for a variety of situations - code is data after all. Regards, Brett. -- To unsubscribe from this list, please send an email to [EMAIL PROTECTED] with "unsubscribe" in the subject, without the quotes.
