To improve the overall quality of the project, we should get rid of
this global variable.

It's a bit problematic, because it serves as a general way of accessing
all the persistent (through the life of the process) data that InitNG
uses.

The simplest way to avoid this is to abstract the access to these
variables through well defined functions.

There are few options to do this, I think the following are viable:

  * A function that uses another function to iterate over the elements
    of the list (a la qsort).
  * A function that returns the needed data to iterate over the list,
    used by a macro to do the job.
  * ­<place here any other idea>

This way we could simplify the design and avoid breaking the API so
often.

-- 
Ismael Luceno

Attachment: signature.asc
Description: PGP signature

--
_______________________________________________
Initng mailing list
[email protected]
http://jw.dyndns.org/mailman/listinfo/initng

Reply via email to