Re: bison shift/reduce conflict

[Christian Hopp]

On Mon, 2 Dec 2002, Martin Pala wrote:

> Jan-Henrik Haukeland wrote:
>
> >Jan-Henrik Haukeland <address@hidden> writes:
> >
> >>There are other choices, if you remove the /* EMPTY */ production
> >>from time and from action the conflict is solved
> >>
> >
> >Actually, it's enough to remove the /* EMPTY */ production from
> >action, maybe it's the simplest thing to do? I think that's going to
> >get my +1.
> >
> I'm +1 too, so time and/or action will be required.
>

Or we define an action statement like,

TIMESTAMP /foo/bar > 5 seconds ACTION alert.

That would solve the shift problem => we would change all "action" related
statements... like resouce.

Christian


-- 
Christian Hopp                                email: address@hidden
Institut für Elektrische Informationstechnik             fon: +49-5323-72-2113
TU Clausthal, Leibnizstr. 28, 38678 Clausthal-Zellerf.   fax: +49-5323-72-3197
                             pgpkey: https://www.iei.tu-clausthal.de/pgp-keys/