On Wed, 13 Mar 2002, Konstantin Zhidkov wrote: > While reading such code one have to look at definition of > *each* function, because there's no other way to distinguish > between conditional and generic functions. Simple naming > convention can overcome this nightmare: cond__<name> > like this: cond__i8259_setup();
I hadn't thought of this. good point. > There's also need to distinguish between configuration options > and configuration parameters. While option can only exist or > not exist, parameter can have any value, including zero, and > can also not exist. Currently, one have to add both option and > parameter to avoid use of #ifndef, for example: we have had so much trouble with the options vs. parameters that I think we should just require parameters. ron
