From: "Matthew Heaney" <mheaney@on2.com>
Subject: Re: Pre-Elaboration clarification.
Date: Wed, 28 Nov 2001 12:55:30 -0500
Date: 2001-11-28T12:55:30-05:00 [thread overview]
Message-ID: <u0a91lan036634@corp.supernews.com> (raw)
In-Reply-To: v59L7.42261$RI2.21722340@news2
"Clueless" <chris@dont.spam.me> wrote in message
news:v59L7.42261$RI2.21722340@news2...
> Are there any basic rules of thumb that an "Intermediate" level
> programmer(as I was declared by my CS teacher) should follow in Ada as
> regards data types and spec files?
In general, you should always defer package dependencies to the body, or to
a child.
> I've made a BIG point of avoiding unecessary coupling as you pointed out.
> As I'm not writing very "large" programs in Ada yet, I havent really run
> into any problems with Data types and elaboration.
My comment wasn't about elaboration issues specifically. But it seemed as
if you had a dependency on package Command_Line in a spec, when it wasn't
strictly necessary.
> Is there anything that
> I should be practicing regularly, which might be peculiar to Ada95, that
> would help me avoid problems once I get into developing "larger" pieces
> of software?
Managing dependencies among compilation units isn't specific to Ada95 -- the
techniques are necessary in C++ as well. You can read John Lakos' Large
Scale C++ Software Design for ideas that apply to either C++ or Ada95.
There's also a section in Norm Cohen's book, about minimizing dependencies
among Ada packages.
next prev parent reply other threads:[~2001-11-28 17:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-05 15:52 Pre-Elaboration clarification Clueless
2001-11-05 17:49 ` Jeffrey Carter
2001-11-09 22:45 ` Matthew Heaney
2001-11-22 15:46 ` Clueless
2001-11-28 17:55 ` Matthew Heaney [this message]
2001-11-28 18:12 ` WAS " Mark Lundquist
2001-11-28 18:46 ` Mark Lundquist
2001-11-28 20:13 ` Matthew Heaney
2001-11-29 9:34 ` Simon Wright
2001-11-10 6:31 ` Robert Dewar
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox