Re: monit CHANGES.txt gc.c l.l monitor.h p.y util.c...

[Jan-Henrik Haukeland]

On Dec 20, 2004, at 11:39 AM, Michael Shigorin wrote:

> On Mon, Dec 20, 2004 at 11:20:19AM +0100, Jan-Henrik Haukeland wrote:
> > > BTW, is it reasonable to put at the back of the head something
> > > like "make separate parser which is called when monit starts
> > > or reloads and doesn't sit in memory with all the libraries
> > > involved full time"?
> > I think you mix-up what parsing and a parser-generator is with
> > something else.
>
> No I don't.

I beg to differ :-) Judging by your use of metaphors and talk about 
runtime and linking I'm not quite convinced that you do not confuse 
this with an interpreter-system like Ruby.

>  It's just a parser (the result being linked in a running monit)

Not into a running monit, it's linked in at compile time into the 
binary executable and not loaded at runtime nor from any dynamic 
library.

> ends up being one-time chunk of code.  It's like
> root partition, when it's small, it's harder for a stray bad
> block to render the whole system unbootable to the minimal state.

It's more like putting the word "world!" into printf("Hello \n");

> When the process image is smaller, it's less prone to being
> swapped out; when its share library deps are tighter, it's less
> prone to ABI breakage and .so corruption, etc.

Once again, there are no dynamic shared object from, or used by the 
parser! Do a ldd on the monit executable and tell me which library you 
see is linked in for parsing? You should compile monit and look closely 
at the what bison and flex output to see what is compiled into monit 
from the grammar files.

On a final note. That monit actually is using a real parser-generator 
and a scanner is a good thing and a token of quality and a guarantee 
for tested and proved code for you as a user. What more it makes it 
possible for us to provide monit with a rather sophisticated control 
file language. That using a parser-generator is a bad thing which you 
seems to imply is a grave misunderstand on how to build a proper 
translator. You wouldn't go to the GCC project and tell them to stop 
using a parser-generator for parsing source code files would you?

--
Jan-Henrik Haukeland
mobile +47 97141255