21 messages in com.perforce.jamming[jamming] Re: Whitespace As Delimiter...
FromSent OnAttachments
Vladimir Prus24 Jul 2001 08:40 
Arnt Gulbrandsen31 Jul 2001 02:23 
Roesler, Randy01 Aug 2001 12:48 
Glen Darling01 Aug 2001 22:23 
Arnt Gulbrandsen02 Aug 2001 03:17 
Roger Lipscombe02 Aug 2001 04:01 
Arnt Gulbrandsen02 Aug 2001 04:09 
Arnt Gulbrandsen02 Aug 2001 04:23 
David Abrahams02 Aug 2001 07:37 
Roesler, Randy02 Aug 2001 21:14 
Roesler, Randy02 Aug 2001 21:31 
Glen Darling02 Aug 2001 22:52 
Paul Haffenden03 Aug 2001 01:57 
David Abrahams03 Aug 2001 06:22 
Arnt Gulbrandsen03 Aug 2001 06:49 
David Abrahams03 Aug 2001 07:03 
Roesler, Randy03 Aug 2001 11:34 
Roesler, Randy03 Aug 2001 11:42 
David Abrahams" <david.abrahams@rcn.com (David Abrahams)03 Aug 2001 16:24 
Glen Darling06 Aug 2001 19:01 
Arnt Gulbrandsen07 Aug 2001 03:12 
Subject:[jamming] Re: Whitespace As Delimiter -- Yuk!
From:Paul Haffenden (pj@unisoft.com)
Date:08/03/2001 01:57:26 AM
List:com.perforce.jamming

Hi,

I would have to agree with the comments that Jam's lexer and parser could be better. We had to increase our Yacc stack to some 50000 nodes to parse our jam rules. Thats because the current grammer is right-recusive instead of left. Another "project" that I never got to :)

Someone posted a fix for this a long time ago, to make it left recursive, and it seems to work for jam2.3.

c) substitution (like ksh's $(var#) $(var~) or perls =~ )

I have done this using a :E modifier in the variable handling, and the code was sent to Perforce. I've since changed the syntax, anyone is welcome to the code (expand.c).

Paul.