It's very useful to me ,,,thank you Jacob,
On 2013-01-16 16:08, o3o wrote:
Let me play with some scenario: I've a library 'acme' release 1.0 and
two client C1 and C2.
* scenario 1: acme in common directory
+ acme
...
+ C1
...
+ C2
...
So, in C1
$dms -I../acme *.d
and in C2
$dms -I../acme *.d
suppose that C2 need a new featur
On Wednesday, 16 January 2013 at 12:00:54 UTC, Jacob Carlborg
wrote:
Thanks for your prompt response.
[cut]
You usually place it in a common directory. You then use the -I
switch to make the compiler aware of this directory.
Let me play with some scenario: I've a library 'acme' release 1.0
a
On 2013-01-16 12:25, o3o wrote:
Suppose I have the following library structure (from Andrei
Alexandrescu 'The D Programming Language' pag. 352)
acme
├── algebra.d
└── io
└── file.d
// acme/algebra.d
module algebra;
import std.stdio;
public void gun() {
writeln("algebra->gun");
}
//
