[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Schema, BNF and parsing

• To: Peter Hunsberger <peter.hunsberger@g...>
• Subject: Re: Schema, BNF and parsing
• From: Andrew Jeavons <apj@a...>
• Date: Fri, 04 Mar 2005 14:48:47 -0500
• Cc: xml-dev@l...
• In-reply-to: <cc159a4a05030410524ec6fc40@m...>
• References: <6.2.0.14.2.20050304124119.048582a0@m...><f5bzmxj5lvu.fsf@e...><6.2.0.14.2.20050304130824.04894eb0@m...><cc159a4a05030410524ec6fc40@m...>

>
>
> From your description I'd guess that every verb/attribute combination
>and interaction has been hardcoded.  If so, you might get the best
>bang for your buck by "acquiring" (training/hiring) someone who can
>help you re-write your existing XSLT.

Exactly. Which is totally brain dead. That's what set me on my search for 
the BNF tool. Even with my minimal XSLT knowledge seeing the SAME code
over and over again made me very worried.....

The XSLT was done by external contractors, soon to be ex-contractors now if 
I can help it. I know that I can make a parser out of Bison and Flex with a 
fifth or less code
which will do far more than the XSLT does and be readable (well to me 
anyway....)

Thank for your help.
Andrew

>--
>Peter Hunsberger

• Follow-Ups:
  • Re: Schema, BNF and parsing
    • From: Bob Foster <bob@o...>

• References:
  • Schema, BNF and parsing
    • From: Andrew Jeavons <apj@a...>
  • Re: Schema, BNF and parsing
    • From: ht@i... (Henry S. Thompson)
  • Re: Schema, BNF and parsing
    • From: Andrew Jeavons <apj@a...>

• Prev by Date: RE: Schema, BNF and parsing
• Next by Date: Re: Schema, BNF and parsing
• Previous by thread: Re: Schema, BNF and parsing
• Next by thread: Re: Schema, BNF and parsing
• Index(es):
  • Date
  • Thread