throopw@bert.dg.com (Wayne A. Throop) (05/03/89)
> ddb@ns.network.com (David Dyer-Bennet) > I've seen quite a few bugs that were finally determined to be caused > by programmers looking at code with identifiers with the same spelling but > different casing, and thinking they were the same. How did this escape the notice of the C compiler? The only case I can think of is if one invokes an implicit external int routine of the wrong name... but that is normally caught at link time. True, C allows one to declare external names instead of importing them, but I essentially never do this... names are entered as a defining instance exactly once. All other mentions in source code are either spelled correctly, or are flagged by the compiler (or linker). Surely the culprit here must be improper and unclean use of external declarations, not problems with "case" per se. After all, the names could differ optically, as in ol and o1 and have the same effect. -- If at first you doubt, doubt again. --- William Bennett -- Wayne Throop <the-known-world>!mcnc!rti!xyzzy!throopw