IRCd:configuration feature
Admin (Talk | contribs)
(New page: The "features" subsystem was originally added to work around the lack of flexibility of IRCu's original configuration file parser. Once ircd-darenet switches to a BIND-style configuration ...)
(New page: The "features" subsystem was originally added to work around the lack of flexibility of IRCu's original configuration file parser. Once ircd-darenet switches to a BIND-style configuration ...)
Current revision as of 19:49, 17 February 2009
The "features" subsystem was originally added to work around the lack of flexibility of IRCu's original configuration file parser. Once ircd-darenet switches to a BIND-style configuration file format, it might be time to replace this subsystem. The new system should include the ability for loaded modules to dynamically add new tunables--which means that unrecognized values should be stored somewhere. Also, some of the getter/setter hacks that were added to support logging configuration can now be removed, as the configuration file can be reworked to directly include logging configuration.
