I agree with Lex...I like Duane's parser, however, I think that the VW
parser will have a much higher likelyhood to be used, extended,
supported, etc.  XML itself is pretty mundane and it would seem a waste
to expend a lot of effort on it when there is so much more to be done.

- Stephen

> -----Original Message-----
> From: squeak-dev-admin at lists.squeakfoundation.org 
> [mailto:squeak-dev-admin at lists.squeakfoundation.org] On 
> Behalf Of Lex Spoon
> Sent: Tuesday, November 27, 2001 10:33 AM
> To: squeak-dev at lists.squeakfoundation.org
> Subject: Re: XML Parser choice (was Re: [ENH] ??? MD5 in Squeak.)
> 
> 
> 
> 
> > Maybe we should agree on a Squeak native (lean mean DTD 
> skipping, SAX) 
> > parser and point to the VW port for applications that need the more 
> > complete implementation the VW port offers.
> > 
> 
> From an outsider's perspective, this seems like a really 
> strange strategy.  Code size isn't a terribly big deal -- the 
> thing the Squeak community is most constrained by is 
> programmer time.  How often does someone post about a really 
> neat idea they have.... but that they don't have time to 
> program?  I'd much rather see SuperSwiki get connected to 
> Jabber, for example, than see a custom XML library.  :)
> 
> Besides, it would seem reasonable to at least *try* to divide 
> the VW parser into subsets, so that you can load whichever 
> parts you need.
> 
> 
> -Lex
> 
>