From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail
From: Victor Porton <porton@narod.ru>
Newsgroups: comp.lang.ada
Subject: Is it worth to separate dependencies into a child package?
Date: Tue, 12 Aug 2014 22:54:09 +0300
Organization: Aioe.org NNTP Server
Message-ID: <lsdrd2$ktp$1@speranza.aioe.org>
NNTP-Posting-Host: AnnUDmZwVERVUXyHDyOl5A.user.speranza.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7Bit
X-Complaints-To: abuse@aioe.org
User-Agent: KNode/4.12.4
X-Notice: Filtered by postfilter v. 0.8.2
Xref: news.eternal-september.org comp.lang.ada:21690
Date: 2014-08-12T22:54:09+03:00
List-Id: <comp.lang.ada>

I do thick bindings for Raptor C library.

I am writing package RDF.Raptor.Statement which operates with so called 
statements.

Among other things which are possible with statements, a statement can be 
written into a stream. For this I need the package (which I have written 
earlier) RDF.Raptor.Iostream.

My question: Is it worth to create a child package 
RDF.Raptor.Statement.Iostreams in order to eliminate the need of package 
specification RDF.Raptor.Statement to "with" RDF.Raptor.Statement.Iostreams?

It is felt intuitively that separating it could be better. But are there 
real benefits? One possible benefit is to decrease the need of re-
compilation while I do the development (however it is not a big problem with 
my i7 computer).

Other arguments to split stream operations or not to split them into a child 
package?

-- 
Victor Porton - http://portonvictor.org