monit-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bison shift/reduce conflict


From: Martin Pala
Subject: Re: bison shift/reduce conflict
Date: Mon, 02 Dec 2002 14:55:48 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020513

Jan-Henrik Haukeland wrote:

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).

OK, i'll change it as soon as i'll be back home (in the evening).






reply via email to

[Prev in Thread] Current Thread [Next in Thread]