From: Niklas Holsti <nobody@nowhere.fi>
Subject: Re: Why should the value for a discriminant be static?
Date: Fri, 11 Feb 2005 09:52:58 +0200
Date: 2005-02-11T09:52:58+02:00 [thread overview]
Message-ID: <420C645A.8070203@nowhere.fi> (raw)
In-Reply-To: z2UOd.5420$UX3.1713@newsread3.news.pas.earthlink.net
Jeffrey Carter wrote:
> Niklas Holsti wrote:
>
>> Now then, that's rather harsh. It's certainly legal Ada; if you think
>> its philosophically faulty, you are entitled to your opinion and I am
>> entitled to disagree; if you think its faulty because it leads to
>> practical problems, the problem is just with the requirement for
>> static discriminants in aggregates -- which is what this thread is
>> about.
>
>
> Not at all. There's a software engineering principle that one thing
> should serve one purpose, and this violates that: it serves both to
> identify the 2 classes and to provide the specific information for each
> class.
So the "fault" is philosophical. From your interpretation of that
principle, you could argue against any use of "derived properties
of objects", and insist on a separate component to hold each such
derived property. Not attractive to me, but as I said, we can
disagree on what is desirable, even if we agree that the current
Ada rules are asymmetrical in this area.
--
Niklas Holsti
Tidorum Ltd
niklas holsti tidorum fi
. @ .
next prev parent reply other threads:[~2005-02-11 7:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 14:30 Why should the value for a discriminant be static? Jacob Sparre Andersen
2005-02-09 18:34 ` Randy Brukardt
2005-02-09 20:16 ` Niklas Holsti
2005-02-10 0:19 ` Jeffrey Carter
2005-02-10 13:11 ` Niklas Holsti
2005-02-11 1:40 ` Jeffrey Carter
2005-02-11 7:52 ` Niklas Holsti [this message]
2005-02-09 22:22 ` Jacob Sparre Andersen
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox