> > This brings up something I posted to the
[....]
> field comes right after the
This looks like a 'making life easy for the parser/making life easy for
output << "ExtNode { fields [ ... ]"; // pick a lanbu, any
to
output << "ExtNode { fields [ ... ] isA [ ... ]";
or something similarly trivial.
In contrast the
The real concern I have about this is for when streaming input becomes
[ I live in New Zealand, and the international link has been really bad
> (minor
> > spec chanb>/clarification). If we want to be able to do partial
> > rendering, the
> > fields (makes sense anyway, but it isn't in the
> restricted as to
>
> In the
> fields and
> field, and after reading the node we look at isA and replace the node with
> a known node, then copy all the fields over.
the authoring tool' tradeoff. If the positioning of the isA field is
unrestricted, then the authoring tool has more
working
will be infinestimal. It'll be a
fields I don't know about _as
lore
until the final isA is read and
bottleneck is probably the network). Especially if you're
lately. I've come to _love_ anything which can recover from a partial
transfer ;) ]
--
Oliver Jowett Student, programmer-at-larb>,
[email protected] and generally nice