Re: evaluating an expression while parsing

2004-07-15 Thread Ted Zlatanov
On Wed, 14 Jul 2004, [EMAIL PROTECTED] wrote: > I think it is better to create an "executable" and then execute it. Isn't this a lot harder to debug? It seems like dumping the contents of a data structure is a lot easier than dumping subroutines. With the high rate of P::RD initial grammar bugs

Re: evaluating an expression while parsing

2004-07-15 Thread Ron D. Smith
On Thursday, Jul 15, 2004 "Ted Zlatanov" said: > On Wed, 14 Jul 2004, [EMAIL PROTECTED] wrote: > > > I think it is better to create an "executable" and then execute it. > > Isn't this a lot harder to debug? It seems like dumping the contents > of a data structure is a lot easier than dumping su

Re: evaluating an expression while parsing

2004-07-14 Thread Ron D. Smith
On Sunday, Jul 11, 2004 "Andrew A. Chen" said: > Hello- > I'm just starting out with PRD here, but I think I'm on the right track. > I'm attempting to write a parser that evaluates a language similar to > SQL's WHERE syntax. I'd also like to evaluate the result of this boolean > expression wit

Re: evaluating an expression while parsing

2004-07-12 Thread Ted Zlatanov
On Sun, 11 Jul 2004, [EMAIL PROTECTED] wrote: > The question here is that I'd like to be able to evaluate the above > statements by passing in some values for num_oranges, num_apples, > has_override, etc. Idealy, I'd like to be able to give it a hashref > with all of these variables and then have