a> But one does have to use an "experimental" version of CMUCL, if one uses a> CMUCL. It's documented on the CL-XML website but I certainly overlooked it
What does "experimental" mean? AFAIK, experimental versions were from years ago. There are, however, some monthly snapshots available[1], with some other random CVS snapshots. And a release is coming Real Soon Now too.
Ray
Footnotes: [1] Sort of. cons.org is mostly down right now. But should be back real soon now.
See http://cl-xml.org and under Availability | Releases follow the "A separate {{document}}" link. to the CL-XML Releases page. The cmucl entry is marked "yes[1]" under the "wo/CL-HTTP w/ name symbols" column. Footnote [1] says "the experimental CLOS/MOP is required. tests were done with the {{i686-linux}} version." The i686-linux link points to http://cvs2.cons.org/ftp-area/cmucl/experimental/pcl/cmucl-2003-03-28... -37-i686-Linux.tar.gz, if I spelled that correctly. CL-XML did not compile with any other version of CMUCL that I had tried but it worked fine with that one.
"Raymond Toy" <t...@rtp.ericsson.se> wrote in message
> a> But one does have to use an "experimental" version of CMUCL, if one uses > a> CMUCL. It's documented on the CL-XML website but I certainly overlooked it
> What does "experimental" mean? AFAIK, experimental versions were from > years ago. There are, however, some monthly snapshots available[1], with > some other random CVS snapshots. And a release is coming Real Soon > Now too.
> Ray
> Footnotes: > [1] Sort of. cons.org is mostly down right now. But should be back > real soon now.
a> marked "yes[1]" under the "wo/CL-HTTP w/ name symbols" column. Footnote [1] a> says "the experimental CLOS/MOP is required. tests were done with the
Ah, ok. That's Gerd's PCL stuff. Yeah, it was experimental, but it's not anymore. It will go out in the next release, and has been the default for quite a while.
there were a number of things which the experimental pcl did better than the then official release at the time i was porting, so i've been waiting for some indication that it had been folded into a stable release before rechecking compatibility and updating any documentation.
if anyone has built it with more recent cvs snapshots, please let me know, so that i can update the notes. otherwise i'll just keep watching the releases.
> a> marked "yes[1]" under the "wo/CL-HTTP w/ name symbols" column. Footnote [1] > a> says "the experimental CLOS/MOP is required. tests were done with the
> Ah, ok. That's Gerd's PCL stuff. Yeah, it was experimental, but it's > not anymore. It will go out in the next release, and has been > the default for quite a while.
Erik Naggum wrote: > * Kenny Tilton > | Maybe I just misunderstood. If quads just give me a link to the > | parent, well, in the case of the DTD, all the entities, elements, and > | attributes had the same parent, the XML dtd document. So I imagined > | an awful lot of serial searching, repeated over and over again for the > | same message type, and yes, I made a gut determination that I could > | use the names of things as keys to a hash table and turn a record > | expansion into so many keyed lookups.
> You assume way too much. I lack the information to unwind your many > assumptions, but you may have noticed that I wrote that QAR would > point to the element type, like the operator in the CAR of a sexpr. > This is obviously a symbol-like structure. For some reason, you have > read what I wrote to refer to the prolog of an SGML/XML document, > while I talked about the document instance.
No, I figured out you must be talking about doc instances. That is why I confessed to parsing a DTD. Anyway, i think I follow. The only reason I thought mad serial searching was involved was the parent pointer, but hey, all my tree nodes know their parents so I certainly see the value in that.
I have written elsewhere
> that the very concept of a DTD was a huge mistake,
It seems the world agrees. The DTD is dead, long live the Schema.
> But I don't know where to begin to explain things to you so you don't > assume things without asking.
This reminds me of my attempt to teach someone rollerblading, who persisted in pitching himself headlong and often spinning thru the air and onto the asphalt. After a few tries at talking the lad down I realized it was just his learning style and let him be.
Anyway, as I said, I have always been a parent-aware node designer myself, so it is fun seeing that elevated to the status of a car or cdr.
Not that it matters, but why isn't the parent the first slot? As for the tail being dotted, bold stroke that. I've always felt bad writing code to ask my parent who is nect after me just to get to my next sibling.
* Kenny Tilton | The only reason I thought mad serial searching was involved was the | parent pointer, but hey, all my tree nodes know their parents so I | certainly see the value in that.
OK, but the point with my approach is to "load" a document into memory and then work on and navigate around in the in-memory representation instead of the edge-detection scheme that is used in the most popular tools. That is, a DOM without any of the insanity.
| It seems the world agrees. The DTD is dead, long live the Schema.
I am not pleased with this development, either, FWIW.
| Not that it matters, but why isn't the parent the first slot?
Because the QAR is the "operator". In the case of an entity fragment, the QAR is the source, and the meaning of the QBR is different, but if the two-dimensional vector with indexes instead of pointers is used, both a parent and a start position in a source would be a number.
| As for the tail being dotted, bold stroke that. I've always felt bad | writing code to ask my parent who is next after me just to get to my | next sibling.
Precisely. That is so wrong.
-- Erik Naggum | Oslo, Norway
Act from reason, and failure makes you rethink and study harder. Act from faith, and failure makes you blame someone and push harder.
