using standard interfaces

[Henry Spencer]

In article <33391 at cca.CCA.COM> g-rh at CCA.CCA.COM (Richard Harter) writes:
>This sounds good, but there is a problem to take into account.  If
>you have your own routine with the same name as the "standard"
>routine there is the potential for problems when you port into
>a system that has the "standard" routine in its library...

This just means that inclusion of the routine in question must be optional,
so it can be disabled on such systems.  No big deal.  Possibly the best way
to do this is to #ifdef the user-supplied routine, so that an explicit -D
option (or whatever) is required to use it.
-- 
NASA is into artificial        |     Henry Spencer at U of Toronto Zoology
stupidity.  - Jerry Pournelle  | uunet!attcan!utzoo!henry henry at zoo.toronto.edu