From: Stefan.Lucks@uni-weimar.de
Subject: Re: Parent/child dependencies and internal library units
Date: Wed, 23 Jul 2014 20:37:18 +0200
Date: 2014-07-23T20:37:18+02:00 [thread overview]
Message-ID: <alpine.DEB.2.11.1407232030230.22347@debian> (raw)
In-Reply-To: <lqoncd$ue7$1@speranza.aioe.org>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 618 bytes --]
On Wed, 23 Jul 2014, Victor Porton wrote:
> What is a good way to create "internal" or "implementation" units for a
> unit? Should I create a *.Internal.* hierarchy of packages?
I am not sure if it is a good way, but I usually define a project-specific
"super package", often just an empty package. Then I define both internal
and external packages as children of the super package.
------ I love the taste of Cryptanalysis in the morning! ------
<http://www.uni-weimar.de/cms/medien/mediensicherheit/home.html>
--Stefan.Lucks (at) uni-weimar.de, Bauhaus-Universität Weimar, Germany--
next prev parent reply other threads:[~2014-07-23 18:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 16:20 Parent/child dependencies and internal library units Victor Porton
2014-07-23 16:40 ` mockturtle
2014-07-23 16:47 ` Simon Wright
2014-07-23 16:48 ` Adam Beneschan
2014-07-23 18:37 ` Stefan.Lucks [this message]
2014-07-23 21:31 ` Robert A Duff
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox