Figured out the best way (IMO) to go about it: seperate API functions,
just like the 'var' command.  It's just easier than screwing around
with some kind of data structure that would have to be poked and
prodded a lot to get variables out of it.

At this point, continuing work on this lib means a few things:

1) Move more functions into it (so that it doesn't depend on Rivet and
   could be used for other Apache Tcl projects).

2) Start using it, removing the duplicate code from some of the
   rivetCore functions.

3) Start work on the CGI version, as well as a 'main' function to
   compile a CGI rivet version.

-- 
David N. Welton
   Consulting: http://www.dedasys.com/
Free Software: http://people.debian.org/~davidw/
   Apache Tcl: http://tcl.apache.org/
     Personal: http://www.efn.org/~davidw/

Reply via email to