Re: keyword list/ecpg

I took a quick look at this - would it be ok to add some small amounts
of 'markup' to the gram.y ?

eg :

/* ECPGCOPYON */
....
/* ECPGCOPYOFF */

/* ECPGMODE=NOSPACE */
...
/* ECPGMODE=USESPACE */

etc ?

On Friday 13 June 2008 10:47:55 Michael Meskes wrote:
> [Sorry, just noticed that I didn't answer this email. ]
>
> On Wed, Jun 04, 2008 at 05:06:41PM +0100, Mike Aubury wrote:
> > It might depend on the tokens..
> > Are ">=", "++" etc single tokens ?
> > ...
> >
> > > Wouldn't it work to just always insert a space between tokens, no
> > > matter whether there was one originally?
>
> There are a few cases where you must not enter a blank, but I'm not sure
> whethere these are all in ecpg specific rules anyway. One example that
> comes to my mind is the handling of ":<port>" in the connect statement.
>
> Michael
> --
> Michael Meskes
> Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
> ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes(at)jabber(dot)org
> Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!

--
Mike Aubury

http://www.aubit.com/
Aubit Computing Ltd is registered in England and Wales, Number: 3112827
Registered Address : Clayton House,59 Piccadilly,Manchester,M1 2AQ