Re: recdescent 2.0 and Perl 6

2004-05-14 Thread Aamer Akhter
Sean O'Rourke wrote: Aamer Akhter [EMAIL PROTECTED] writes: We're starting a project that includes a parser that would convert a huge swath of multi-device output (output of explicit commands) to an XML tokenized form. ... I've written parse::recdescent grammars for some of this output in the

architectures for organizing grammars

2004-05-14 Thread Aamer Akhter
Hello, This is really an open-ended question... and I pre-apologize for my rambling style. So far all the examples of grammars I've seen are free standing on their own. We're eval'ing prd for providing xmlization services for a lot of varied output. It'll be mostly router output (from a

suppressing __VALUE__ in autotree

2004-05-14 Thread Aamer Akhter
Hello, Is there a way of supressing the __VALUE__ hash that is added via a single terminal return in autotree? Right now I have to play silly little games on the return values. I realize that I could add my own return handler but autotree is _so_ nice otherwise. aa

RE: Using $skip='[ \t]+' to parse line(s)

2004-05-14 Thread Alexander.Farber
Just FYI, I've registered a perl bug for that issue http://rt.perl.org/rt3/Ticket/Display.html?id=29576 -Original Message- From: ext [mailto:[EMAIL PROTECTED] use strict; use vars qw($parser $text %hol); use Data::Dumper; use Parse::RecDescent; $Parse::RecDescent::skip = '[

Re: keyword value(s) newline

2004-05-14 Thread Karl Gaissmaier
Ron D. Smith schrieb: ... Um the technical term for this is hell if I know. If you are irritated by it now, imagine how irritating it gets when the file you are parsing is HUGE and you get the whole thing for each an every attempt... (I modified the PR::D source to truncate the output

RE: Using $skip='[ \t]+' to parse line(s)

2004-05-14 Thread Alexander.Farber
Sorry for one more mail, but just for the record: that has been my own fault. My both problems (KEY1 = 'undef' and having to use ref $item{value}) were caused by these change in P:RD: - BACKWARDS INCOMPATIBLE CHANGE: The key of an %item entry for a repeated subrule now includes the repetition

Re: suppressing __VALUE__ in autotree

2004-05-14 Thread Ted Zlatanov
On Thu, 13 May 2004, [EMAIL PROTECTED] wrote: Is there a way of supressing the __VALUE__ hash that is added via a single terminal return in autotree? Right now I have to play silly little games on the return values. I realize that I could add my own return handler but autotree is _so_ nice

Re: suppressing __VALUE__ in autotree

2004-05-14 Thread Aamer Akhter
On May 14, 2004, at 10:26 AM, Ted Zlatanov wrote: On Thu, 13 May 2004, [EMAIL PROTECTED] wrote: Is there a way of supressing the __VALUE__ hash that is added via a single terminal return in autotree? Right now I have to play silly little games on the return values. I realize that I could add my