Re: [fpc-pascal] fpc-passrc expression parser (issue #16914)

2010-07-15 Thread Michael Van Canneyt
On Thu, 15 Jul 2010, dmitry boyarintsev wrote: On Tue, Jul 13, 2010 at 12:42 PM, Michael Van Canneyt mich...@freepascal.org wrote: I must say that I am not familiar with the parsing style you used. I wrote 2 expression parsers meanwhile, and both used a different style. see

Re: [fpc-pascal] fpc-passrc expression parser (issue #16914)

2010-07-14 Thread Michael Van Canneyt
On Wed, 14 Jul 2010, Paul Nicholls wrote: - Original Message - From: Michael Van Canneyt mich...@freepascal.org To: FPC-Pascal users discussions fpc-pascal@lists.freepascal.org Sent: Tuesday, July 13, 2010 6:42 PM Subject: Re: [fpc-pascal] fpc-passrc expression parser (issue #16914

Re: [fpc-pascal] fpc-passrc expression parser (issue #16914)

2010-07-14 Thread Marco van de Voort
In our previous episode, Paul Nicholls said: Michael. Hi all, I am interested in expression parsers myself :) Where can I find the code for fpexprpars.pp and other fpc parsing code like that? I had bit of a look browsing the SVN online, but no luck... That one is in

Re: [fpc-pascal] fpc-passrc expression parser (issue #16914)

2010-07-13 Thread Michael Van Canneyt
On Tue, 13 Jul 2010, dmitry boyarintsev wrote: Hello, Michael Van Canneyt, Sorry, I can't write to the resolved issue (without re-opening) it. - better class tree (split out binary/unary/primitive operators in subclasses) These may break backwards compatiblity; if you prefer to do them

Re: [fpc-pascal] fpc-passrc expression parser (issue #16914)

2010-07-13 Thread Paul Nicholls
- Original Message - From: Michael Van Canneyt mich...@freepascal.org To: FPC-Pascal users discussions fpc-pascal@lists.freepascal.org Sent: Tuesday, July 13, 2010 6:42 PM Subject: Re: [fpc-pascal] fpc-passrc expression parser (issue #16914) On Tue, 13 Jul 2010, dmitry boyarintsev

[fpc-pascal] fpc-passrc expression parser (issue #16914)

2010-07-12 Thread dmitry boyarintsev
Hello, Michael Van Canneyt, Sorry, I can't write to the resolved issue (without re-opening) it. - better class tree (split out binary/unary/primitive operators in subclasses) These may break backwards compatiblity; if you prefer to do them yourself, I can say what I have in mind. That's how