True, but in order for yacc (or antlr) to generate C# code you have to use their syntax. This syntax is used to provide the so called grammar mentioned by Jiri. In General those kind of tools are basically small "compilers" which parses a given piece of "grammar" and then construct lexical analyzers. Changes in the syntax of the "grammar" tends to be breaking changes by nature!
> -----Ursprüngliche Nachricht----- > Von: Геннадий Забула [mailto:zabulu...@gmail.com] > Gesendet: Montag, 5. Oktober 2015 16:43 > An: For users and developers of the Firebird .NET providers <firebird-net- > provi...@lists.sourceforge.net> > Betreff: Re: [Firebird-net-provider] Parser class/library > > IIRC, yacc\lex are an external tools that produce .cs files that provide > parsing. > > > On 5 October 2015 at 17:31, Amro El-Fakharany <amro00...@gmail.com> > wrote: > > I would be very careful taking a dependency on an external library like yacc > or antlr and would recommend to avoid such a path. > > If at all a standalone "light weight" tokenizer should be preferable > although, unfortunately, I don’t know any. > > Libraries like antlr and yacc are simply awesome but changes in such > libraries tends to be breaking changes! > > > > > >> -----Ursprüngliche Nachricht----- > >> Von: Геннадий Забула [mailto:zabulu...@gmail.com] > >> Gesendet: Montag, 5. Oktober 2015 16:22 > >> An: For users and developers of the Firebird .NET providers > >> <firebird-net- provi...@lists.sourceforge.net> > >> Betreff: Re: [Firebird-net-provider] Parser class/library > >> > >> EF uses yacc and lex for EntityTree parsing. > >> They both produce C# class that can be compiled into the assembly. > >> > >> On 5 October 2015 at 16:30, Jiří Činčura <j...@cincura.net> wrote: > >> > Hi, > >> > > >> > I'm working on a bug fix for DNET-266. And the more and more I > >> > tweak the parser I wrote this morning to properly handle all the > >> > edge cases I'm wondering whether it would make sense to take a > >> > dependency on > >> some > >> > library or class that can do some basic parsing. We don't need full > >> > grammar features like ANTLR, just something that can tokenize SQL > >> > and handle comments (or in general tokenizer with "escaping" support). > >> > > >> > What do you think? Any recommendations? > >> > > >> > BTW the bugfix is sponsored by SMS-Timing. Kudos to them. > >> > > >> > -- > >> > Mgr. Jiří Činčura > >> > Independent IT Specialist > >> > > >> > ------------------------------------------------------------------- > >> > --- > >> > -------- _______________________________________________ > >> > Firebird-net-provider mailing list > >> > Firebird-net-provider@lists.sourceforge.net > >> > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider > >> > >> --------------------------------------------------------------------- > >> --------- _______________________________________________ > >> Firebird-net-provider mailing list > >> Firebird-net-provider@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/firebird-net-provider > > > > > > ---------------------------------------------------------------------- > > -------- _______________________________________________ > > Firebird-net-provider mailing list > > Firebird-net-provider@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider > > ------------------------------------------------------------------------------ > _______________________________________________ > Firebird-net-provider mailing list > Firebird-net-provider@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider ------------------------------------------------------------------------------ _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
