[Mono-devel-list] RFC: how to manage almost duplicate parser/tokenizer
Atsushi Eno
atsushi at ximian.com
Wed Mar 16 16:43:37 EST 2005
Hi,
I wonder which is the best way to have "almost duplicate" but
different parser/tokenizer pair for XSLT "Pattern" apart from
XPath (I'm going to fix a bug that allows improper XPath for
XSLT pattern e.g. namespace::*).
With my way to do, they could be generated by attached patches:
$ patch -i pattern-parser.diff System.Xml.XPath/Parser.jay -o
System.Xml.XPath/PatternParser.jay
$ patch -i pattern-parser.diff System.Xml.XPath/Tokenizer.cs -o
System.Xml.XPath/PatternTokenizer.cs
$ patch -i use-pattern-parser.diff
... but I wonder if there are better ways to do handle those
parser/tokenizer stuff, because parser/tokenizer patches are easy
to become broken when we fix XPath parser and/or tokenizer sources.
Would it be better if I just put another parser/tokenizer pair?
Atsushi Eno
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: pattern-parser.diff
Url: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20050317/b90afc9b/attachment.pl
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: pattern-tokenizer.diff
Url: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20050317/b90afc9b/attachment-0001.pl
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: use-pattern-parser.diff
Url: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20050317/b90afc9b/attachment-0002.pl
More information about the Mono-devel-list
mailing list