Has anyone worked on improving the default nsd.tcl file structure? For
new users, and for users wanting to try something new, the lack of
documentation and default values for the different modules makes
experimentation difficult.
So here are some random thoughts:
Move module configuration into separate files. Handle all explaination
and variable setting at the top of these files, source the module file
iff it is actually used in the main nsd.tcl file.

Or do the same with a single file, but enclose the module sections
inside ifs conditioned on whether the module is used.

My overall impression is that some solution that allowed the developer
to concentrate on the top part of the file for setting well named, and
maybe commented, variables would be much easier to setup and maintain.

--Tom Jackson

Reply via email to