Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!orstcs!usenet!jacobs.CS.ORST.EDU!keffert
From: keffert@jacobs.CS.ORST.EDU (Thomas Keffer)
Newsgroups: comp.lang.c++
Subject: Re: Naming Conventions
Message-ID: <1991Jan12.225851.6764@usenet@scion.CS.ORST.EDU>
Date: 12 Jan 91 22:58:51 GMT
References: <60352@microsoft.UUCP> <CIMSHOP!DAVIDM.91Jan9105408@uunet.UU.NET> <278D1767.505@tct.uucp>
Sender: @usenet@scion.CS.ORST.EDU
Organization: Oregon State University, CS Dept.
Lines: 29
Nntp-Posting-Host: jacobs.cs.orst.edu

In article <278D1767.505@tct.uucp> chip@tct.uucp (Chip Salzenberg) writes:
>According to cimshop!davidm@uunet.UU.NET (David S. Masterson):
>>// File - complex.ths
>>#ifndef THESAURUS_OFF
>>#ifndef COMPLEX_THS
>>#define COMPLEX_THS
>>
>>#define Complex complex
>>#define COMPLEX complex
>>#define ThisIsComplex complex
>>// ...
>>
>>#endif
>>#endif
>
>Aargh!  It's hard enough to read a mix of other people's code, without
>making one class available under <n> names.

Indeed!  In fact, there are more subtle differences between the various types
of complex than their names: some pass arguments by reference into functions,
some by value, etc.   This matters when one must pass a pointer to the
function for use by "forEach" functions iterating over vector elements, etc.

-tk
___
Thomas Keffer
Rogue Wave
PO Box 2328; Corvallis, OR 97330
(503) 745-5908