Re: bison shift/reduce conflict

[Jan-Henrik Haukeland]

Martin Pala <address@hidden> writes:

> >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
> >
> >
> It could be good solution and in the case that we don't break backward
> compatibility, i would preffer it (to add ACTION statement to the
> grammar and correct documentation). However i think it can affect
> upgrade from 3.0->3.1 so maybe we should just avoid EMPTY (default
> value). What about it? Shall we add ACTION or remove EMPTY from time?

Lets remove /* Empty */ from action it makes more sense also since the
statement then looks like this (in verbose form)

if timestamp /foo/bar > 5 seconds then alert

Which, is a whole lot more logical than:

if timestamp /foo/bar > 5 seconds then ? or
if timestamp /foo/bar > 5 seconds then action ? 

(and the user has to consult the doc to find out that no action i.e. ?
means alert).

-- 
Jan-Henrik Haukeland