Re: [Firebird-net-provider] Parser class/library

der@lists.sourceforge.net> Betreff: Re: [Firebird-net-provider] Parser class/library On Mon, Oct 5, 2015, at 21:32, Michał Ziemski wrote: > IMHO you won't be able to handle all the corner cases without full > grammar parser. Well, the cases we need are not that wide. But it's tedious anyway. &

Re: [Firebird-net-provider] Parser class/library

On Tue, Oct 6, 2015, at 13:16, Amro wrote: > To get more concrete can you provide examples of all relevant corner > cases? If I would knew all of them it would not be corner case. It's just a lot of playing. -- Mgr. Jiří Činčura Independent IT Specialist

Re: [Firebird-net-provider] Parser class/library

Talking about corner cases. Would anybody here mind sending me some statements that mix comments, literals, SET TERMs, etc. in some crazy ways? I think the new parser - which handles comments and is also faster - is getting ready to real tests. :) -- Mgr. Jiří Činčura Independent IT Specialist

Re: [Firebird-net-provider] Parser class/library

Windows Phone From: Jiří Činčura<mailto:j...@cincura.net> Sent: ‎6/‎10/‎2015 6:38 To: For users and developers of the Firebird .NET providers<mailto:firebird-net-provider@lists.sourceforge.net> Subject: Re: [Firebird-net-provider] Parser class/library On Mon,

Re: [Firebird-net-provider] Parser class/library

On Mon, Oct 5, 2015, at 21:32, Michał Ziemski wrote: > IMHO you won't be able to handle all the corner cases without full > grammar > parser. Well, the cases we need are not that wide. But it's tedious anyway. > For example consider a "SET TERM" inside an "EXECUTE BLOCK". > Lacking the grammar

Re: [Firebird-net-provider] Parser class/library

Hi! IMHO you won't be able to handle all the corner cases without full grammar parser. For example consider a "SET TERM" inside an "EXECUTE BLOCK". Lacking the grammar understnding you won't recognize that as an invalid term in the execute block and you'll simply cut the block in half. So the

Re: [Firebird-net-provider] Parser class/library

rge.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, >

Re: [Firebird-net-provider] Parser class/library

http://entityframework.codeplex.com/SourceControl/latest#src/EntityFramework/Core/Common/EntitySql/GenerateParser.cmd On 5 October 2015 at 17:22, Геннадий Забула wrote: > EF uses yacc and lex for EntityTree parsing. > They both produce C# class that can be compiled into the

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 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

Re: [Firebird-net-provider] Parser class/library

pers of the Firebird .NET providers 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..