From: "Jeffrey R. Carter" <spam.jrcarter.not@spam.not.acm.org>
Subject: Re: Code organization
Date: Thu, 27 Sep 2018 21:49:06 +0200
Date: 2018-09-27T21:49:06+02:00 [thread overview]
Message-ID: <pojc7m$fmd$1@dont-email.me> (raw)
In-Reply-To: <f83642f8-7e25-43ae-9ed3-377b53b2bb5c@googlegroups.com>
On 09/27/2018 05:09 PM, NiGHTS wrote:
>
> Then you get into the coding and realize Ada doesn't exactly agree with your organization strategy and imposes some design constraints, particularly with a heavily multi-threaded project. This is kind of how it worked out for me. Once Ada forced me into nesting what would have otherwise been living in other packages, my ambitions for file organization went down the drain. And it didn't help that I was on strict deadline by this point in time.
This has not been an issue for me. A basic principle for me is to avoid writing
executable code for as long as possible (though I write specs as soon as
possible). On tool I use for this is subunits ("separate"), which you are
investigating in other posts, so perhaps we reached similar destinations by
different paths.
--
Jeff Carter
"You cheesy lot of second-hand electric donkey-bottom biters."
Monty Python & the Holy Grail
14
next prev parent reply other threads:[~2018-09-27 19:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 14:24 Code organization NiGHTS
2018-09-27 14:43 ` Shark8
2018-09-27 15:01 ` NiGHTS
2018-09-27 15:33 ` NiGHTS
2018-09-27 14:48 ` Jeffrey R. Carter
2018-09-27 15:09 ` NiGHTS
2018-09-27 19:49 ` Jeffrey R. Carter [this message]
2018-09-27 20:46 ` Brian Drummond
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox