Thomas,

On Thursday 15 May 2008 23:30, Thomas Reinke wrote:
> Some thoughts we've had:
>
>     1) Change the nasl "compiler" to force all variables to be
>        explictly declared;
>     2) Default undeclared variables to a local scope;
>     3) Have a "lint" style checker that examined functions and
>        warned of global variable usage, which could then be vetted
>        as acceptable (or not)
>
> Any thoughts?

It would be great if you could prepare a simple NASL script
that demonstrates the danger of the current NASL implementation.
This script could also then serve for debugging and proof it works
better after a change.

Given there really is the weakness you mention (I didn't track down your
hints yet), option 3 seems not really an option to me.
The first option appears as the best solution to me. This should
reduce programming errors.

Best

        Jan

-- 
Dr. Jan-Oliver Wagner                                   Intevation GmbH
Amtsgericht Osnabrück, HR B 18998             http://www.intevation.de/
Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
_______________________________________________
Openvas-discuss mailing list
[email protected]
http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss

Reply via email to