[arc-discuss] When should interfaces be private?
Philip Brown
ppb at usc.edu
Fri May 2 09:25:38 PDT 2008
Alan Coopersmith wrote:
> Philip Brown wrote:
>> Thus, my position is; ALL interfaces should be documented to some degree,
>> and NO interface should be allowed to be called "private"
>
> Every function call? Every macro? Would you abolish "static" functions
> as well, since those are just another form of "private"?
>
> Sounds like the fastest way to chase away every engineer who would ever
> possibly want to work on the code. Not everything that can be used as
> an interface should be.
Well, I guess we should then define what we mean when we say "an interface",
for this discussion, then :-}
I dont consider "all macros and function calls" to be in the scope of this
discussion.
Rather, "[this 'code module' over here] interacts with [that 'code module'
over there]. How they interact, is 'an interface'"
I guess there's still some ambiguity about, "how big is a code module?"
Well, let's say, "something big enough to get the ARC's attention".
There. problem solved? :-D
More information about the arc-discuss
mailing list