From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Alexander G. M. Smith" <agmsmith@rogers.com>
Subject: Re: programming methodology terminology
Date: Wed, 01 Feb 2006 20:34:41 -0500 EST
Message-ID: <78426832169-BeMail@AlexDualP3>
References: <43DDBD1D.6030900@namesys.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <reiserfs-list-return-27976-reiserfs=m.gmane.org@namesys.com>
list-help: <mailto:reiserfs-list-help@namesys.com>
list-unsubscribe: <mailto:reiserfs-list-unsubscribe@namesys.com>
list-post: <mailto:reiserfs-list@namesys.com>
Errors-To: flx@namesys.com
In-Reply-To: <43DDBD1D.6030900@namesys.com>
List-Id: <reiserfs-devel.vger.kernel.org>
To: Hans Reiser <reiser@namesys.com>
Cc: Reiserfs mail-list <Reiserfs-List@namesys.com>

Hans Reiser wrote on Sun, 29 Jan 2006 23:15:41 -0800:
> When you use a return value #define for two different meanings,
> is there a name for that?  It is generally accepted to be bad
> style, yes?

It might be called something overloading, perhaps Semantic Overloading?

- Alex