• From: John Cowan <cowan@m...>
• To: Uche Ogbuji <uche@o...>
• Date: Mon, 6 Feb 2012 21:27:44 -0500

Uche Ogbuji scripsit:

> If that were the case then writing XML parsers would not be one of the more
> challenging tasks any programmer can face.

I wouldn't call it challenging; it's just full of unfortunate corner cases.
Writing a C++ parser, now that's challenging.

-- 
He made the Legislature meet at one-horse       John Cowan
tank-towns out in the alfalfa belt, so that     cowan@c...
hardly nobody could get there and most of       http://www.ccil.org/~cowan
the leaders would stay home and let him go      --H.L. Mencken's
to work and do things as he pleased.              Declaration of Independence

• Follow-Ups:
  • Re: Should one adopt the tag naming convention of anexisting XML vocabulary or create one's own tag naming convention?
    • From: Uche Ogbuji <uche@o...>

• References:
  • Re: Should one adopt the tag naming convention of anexisting XML vocabulary or create one's own tag naming convention?
    • From: Uche Ogbuji <uche@o...>
  • RE: Should one adopt the tag naming convention of anexisting XML vocabulary or create one's own tag naming convention?
    • From: "Cox, Bruce" <Bruce.Cox@U...>
  • RE: Should one adopt the tag naming convention of anexisting XML vocabulary or create one's own tag naming convention?
    • From: "Costello, Roger L." <costello@m...>
  • Re: Should one adopt the tag naming convention of an existing XML vocabulary or create one's own tag naming convention?
    • From: Petite Abeille <petite.abeille@g...>
  • Re: Should one adopt the tag naming convention of anexisting XML vocabulary or create one's own tag naming convention?
    • From: Greg Hunt <greg@f...>
  • Re: Should one adopt the tag naming convention of anexisting XML vocabulary or create one's own tag naming convention?
    • From: cbullard@h...
  • Re: Should one adopt the tag naming convention of anexisting XML vocabulary or create one's own tag naming convention?
    • From: Uche Ogbuji <uche@o...>