(...that work in AOLserver.)
So, I've been writing Tcl for AOLserver since it only ran Tcl 7.4, and you
only had 3 choices for storing data in Tcl -- scalars, lists and arrays.
Things like a list of arrays weren't possible; if you wanted to have such
a thing, you had to fake it. I admit, I've
I swear, I knew this had been discussed before, I just was looking for
pointers. I found the right set of things to ask Google, and came up with
these
http://www.pinds.com/acs-tips/tcl-data-structures
Lars doesn't believe Tcl is good for this stuff
http://mini.net/tcl/2995
The
Humm, I never really found the short list of data types a hinderance for
Tcl. I have always been able to manage with what is there, although I
did write the record package (tcllib) to overcome one obstacle I had,
but I did that more as an excercise really.
If you really are stuck, and want to
So, I've been writing Tcl for AOLserver since it only ran Tcl 7.4, and you
only had 3 choices for storing data in Tcl -- scalars, lists and arrays.
Things like a list of arrays weren't possible; if you wanted to have such
a thing, you had to fake it. I admit, I've gotten used to being able to
On 2003.01.17, Peter M. Jansson [EMAIL PROTECTED] wrote:
(...that work in AOLserver.)
[...]
Things like a list of arrays weren't possible; if you wanted to have
such a thing, you had to fake it. [...] How do Tcl programmers
normally do such things?
Generally, when I find myself needing
I got this...
On Fri, 17 Jan 2003, Dossy wrote:
Generally, when I find myself needing things like, say, a list of
arrays, in Tcl, they tend to be design smells. It's the I can write
Perl in any language! syndrome.
...and this:
On Fri, 17 Jan 2003, Brett Schwarz wrote:
I am just curious,
On Fri, Jan 17, 2003 at 10:19:27PM -0500, Peter M. Jansson wrote:
I got this...
On Fri, 17 Jan 2003, Dossy wrote:
Generally, when I find myself needing things like, say, a list of
arrays, in Tcl, they tend to be design smells. It's the I can write
Perl in any language! syndrome.
...and
Right or wrong I normally leave that kind of work up to the database rather
than caching it in memory.
I wonder how it would work to write a sql-based database in memory for cache
handling.
Something like:
ns_db cache $postgres select * from postgresql to $ram
ns_db select $ram
