> I've been working a bit on what seemed to me a bug at first
> (we discussed on the list this problem about one year ago).
> Some of the documented commands of rivet ('[un]escape_string'
> and others) where not available to the interpreter.
> A close look at the code shows that librivet.so (which has
> the functions for these commands) was not meant to be a
> shared library linked to mod_rivet.so but a full fledged
> Tcl package that can be yanked in by tcl scripts with the
> usual 'package require' command.
>
> The package name is 'Rivet'. It looks to me an arguable choice
> unless the authors had in mind some sort of major reorganization
> of the rivet commands. 'Rivet' (the package) provides 2 other
> (undocumented ?) sets of commands: a simple cryptographic
> system (a data obfuscation method ?) and a set of improved
> list objects manipulation methods inspired by Tclx.
> I don't even know if the code for these module is tested.
As far as I'm concerned, you can change the name. If anyone squawks,
we'll know that they didn't like it. But they should probably be on
this list in any case...
> To say the least a minimal documentation for these commands
> is needed and the current documentation should be updated
> for those commands that need a 'package require Rivet' in order
> to be available. I can do it, but I was wondering what the
> authors had in mind: continuing the pursuit of their goals
> would probably be a good option and could be part of the work
> we are doing
At one point in time, my idea was a minimalistic core, with lots of
readily available extensions. I don't think that's the wisest course
of action these days. Who cares about saving a few bytes.
> My opinion is that coming up with a 1_0 release that
> compiles only for apache1.x is not a option anymore.
I think that's a sensible point of view. It would look a little bit
ridiculous. Let's call it 2.0 :-)
> Apache2 has been out for too long now and we have to
> continue the development. Nonetheless having a 1_0
> with complete documentation, a good code structure
> and build system could help the work in trunk.
--
David N. Welton
http://www.welton.it/davidw/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
