On Dec 5, 2007 10:08 AM, Nick Kostirya <[EMAIL PROTECTED]> wrote: > Maybe I need to present the data some other way ?
A kdb style table implemented in J would include a boxed list of column data. (Each column would be in its own box). But k/q have quite a bit more complexity to their tables than just this, and also strip out quite a bit of general purpose code support so that its operations are fast and lean. kdb style tables also include names for each columns, and you can identify some collection of columns as primary keys. kdb data structures include triggers (run this calculation when this data gets updated) and dependencies (update update this data structure with this calculation when that other data gets updated). In contrast, J focuses more on functions and their results. We have some support for memory mapped files, which behaves in a more "k-style" fashion, but the core language is more function oriented and less file oriented. In contrast a J array, implemented in K, would be a pair of lists. (one for shape and the other for data), and you would need to implement rank and array formatting and so on, on top of this. I am not sure if K or Q could support user defined adverbs and conjunctions (it seems like it ought to, I just don't know enough of those languages to say how). I hope this helps, -- Raul ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
