From: Jacob Sparre Andersen <jacob@jacob-sparre.dk>
Subject: Re: Tagged type naming convention
Date: Sun, 05 Nov 2017 20:01:00 +0100
Date: 2017-11-05T20:01:00+01:00 [thread overview]
Message-ID: <87y3nkft3n.fsf@jacob-sparre.dk> (raw)
In-Reply-To: 2689fb89-cbde-4d32-9944-4c4c10c34e5e@googlegroups.com
Jere <jhb.chat@gmail.com> writes:
> I was looking at an older document for a naming convention for tagged
> types and stumbled upon J.P. Rosen's "A Naming Convention for Classes
> in Ada 9X" [1]. It's pretty intriguing and, even though it was
> developed for 9X, it has applicability in the current Ada revision.
> However, I haven't really seen it employed in any of the libraries
> I've messed with. Keep in mind, my experience with external libraries
> is limited. I was curious if this style is something that a lot of
> people use and had some input on. Is it still in use? Pros/Cons
> based on experience using it?
It is definitely still in use. I use it.
> One concern for it is consistency. It was presented with tagged types
> in mind, but even non tagged types provide inheritance and primitive
> operations that can be overridden. Should it be applied to those as
> well if used?
Only if you stick to the pattern of a single type per package.
I only use Jean-Pierres's naming pattern for the primary type in a
package. Any "helper" types have more arbitrary names.
Jean-Pierre's naming pattern is one of the two suggested in the Ada 95
Quality and Style Guide.
Greetings,
Jacob
--
Better save than sorry!
next prev parent reply other threads:[~2017-11-05 19:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-04 16:50 Tagged type naming convention Jere
2017-11-04 23:43 ` Luke A. Guest
2017-11-07 0:32 ` Jere
2017-11-05 19:01 ` Jacob Sparre Andersen [this message]
2017-11-07 0:43 ` Jere
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox