On 13 Jan 2003, Michel Arboi wrote:
> > Wishlist Item: When there is an ambiguous use of precedence, NASL might
> > issue a warning about it (exactly like gcc does) ?
>
> Mmmm... Too complex I am afraid.
I am not sure whether gcc does it this way but I think you can add an
"explicit parentheses flag" (EPF) to every operator node in the parse tree
and check for an existence of two operator nodes such that one is the
parent of another, the pair of operators they represent has confusing/
ambiguous precedence and the child node has its EPF unset.
Somewhat tedious but feasible.
--Pavel Kankovsky aka Peak [ Boycott Microsoft--
http://www.vcnet.com/bms ]
"Resistance is futile. Open your source code and prepare for assimilation."