* Is it worth to separate dependencies into a child package?
@ 2014-08-12 19:54 Victor Porton
0 siblings, 0 replies; only message in thread
From: Victor Porton @ 2014-08-12 19:54 UTC (permalink / raw)
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2014-08-12 19:54 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-08-12 19:54 Is it worth to separate dependencies into a child package? Victor Porton
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox