From: Christian Iversen <chrivers@iversen-net.dk>
To: reiserfs-list@namesys.com
Subject: Re: programming methodology terminology
Date: Tue, 31 Jan 2006 07:04:53 +0100 [thread overview]
Message-ID: <200601310704.53929.chrivers@iversen-net.dk> (raw)
In-Reply-To: <43DDBD1D.6030900@namesys.com>
On Monday 30 January 2006 08:15, Hans Reiser wrote:
> suppose there are two distinct layers of abstraction, one on top of the
> other. Suppose someone uses the error condition names of the top layer
> in coding the bottom layer when the return values it is used for in the
> bottom layer have not the same purpose as those of the top layer, and
> when it would be an error for the return value to actually get
> propagated all the way out of the top layer. What is this bad
> programming practice called, there is a name for it isn't there? 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?
I'd say it's definitely a layering violation - but I don't know if there's a
more specific name for this particular situation.
--
Regards,
Christian Iversen
next prev parent reply other threads:[~2006-01-31 6:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-30 7:15 programming methodology terminology Hans Reiser
2006-01-30 7:58 ` Ivan Pulleyn
2006-01-31 6:04 ` Christian Iversen [this message]
2006-02-02 1:34 ` Alexander G. M. Smith
2006-02-02 1:49 ` Hans Reiser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200601310704.53929.chrivers@iversen-net.dk \
--to=chrivers@iversen-net.dk \
--cc=reiserfs-list@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.