cfengine-develop
[Top][All Lists]
Advanced

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

RE: [Cfengine-develop] Development plan / meeting


From: Bas van der Vlies
Subject: RE: [Cfengine-develop] Development plan / meeting
Date: Mon, 3 Mar 2003 14:01:33 +0100

I will reply to the two messages.

> -----Original Message-----
> From: Andrew Stribblehill [mailto:address@hidden
> Sent: maandag 3 maart 2003 13:42
> To: address@hidden
> Subject: Re: [Cfengine-develop] Development plan / meeting
> 
> 
> Quoting Mark Burgess <address@hidden> (2003-03-03 11:55:08 GMT):
> > 
> > Quoting Bas:
> > >  - If the parser/lexer is rewritten. We can remove a lot of code
> > >    from cfengine. Like checking if we suppply the right keywords
> > >    with the right values, eg: Now there are checks everywhere
> > >    if we supplied a integer to a keyword. I personnaly think
> > >    that this will make the cfengine source more readable, 
> > >    extendable and maintenable.
> > > 
> > 
> > I suggest that, along side the current cfengine development,
> > someone prototypes a "mockup" new parser, showing the
> > structure and grammar.
> > 
> > That can be incorporated at a later stage. It is such an important
> > thing to get right that we need a "toy model" before we can
> > do anything "for real".
> 
I agree. Shall we define a project for it?


> Forgive me if I get my terminology wrong -- I'm another of those
> former physicists and never did any formal compiler work...
> 
> What are the types that we need to handle? Obviously, strings and
> integers. Should permissions be a basic type? How about booleans? IP
> ranges? Enums?
> 
> At present, we're parsing a lot as if it's a string, then at
> work-time, checking to see if it makes sense. With some well-chosen
> basic types we can move loads of checking to the parse stage and
> simplify code.
> 
> -- 

All those thing can be checked at parse time. So that we will reduce/
simplify the code.

> 
> _______________________________________________
> Cfengine-develop mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/cfengine-develop
> 




reply via email to

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