Nmap Security Scanner
*Intro
*Ref Guide
*Install Guide
*Download
*Changelog
*Book
*Docs
Security Lists
*Nmap Hackers
*Nmap Dev
*Bugtraq
*Full Disclosure
*Pen Test
*Basics
*More
Security Tools
*Pass crackers
*Sniffers
*Vuln Scanners
*Web scanners
*Wireless
*Exploitation
*Packet crafters
*More
Site News
Site Search:
Exploit World
Advertising
About/Contact
Credits
Sponsors:
edgeos



Nmap Development: Re: [NSE] Shared Script Environments for Threads & Universal Awareness

Re: [NSE] Shared Script Environments for Threads & Universal Awareness

From: Patrick Donnelly <batrick.donnelly_at_gmail.com>
Date: Mon, 30 Jun 2008 20:16:58 -0600

On Mon, Jun 30, 2008 at 6:18 PM, jah <jah_at_zadkiel.plus.com> wrote:
>> Since we're using this nomenclature for script-specific information,
>> how about
>> making a global _R the registry interface? It gets pretty ugly sometimes
>> trying to deal with some arguments, e.g.:
>>
>> nmap.registry.args.anonFTP.pass
> I'm for _R too!
> whois.nse has:
>
> nmap.registry.whois.cache[host.ip].data
>
> which has to be writeable from all threads so cannot be copied into a
> local variable with a shorter name.
>
> _R.cache[host.ip].data
>
> would be much nicer...

This can and should be solved by local variables.

local registry = nmap.registry;
local args = registry.args;

-- 
-Patrick Donnelly
"One of the lessons of history is that nothing is often a good thing
to do and always a clever thing to say."
-Will Durant
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org
Received on Jun 30 2008
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]
edgeos