On Wednesday, 26 October 2016 at 05:46:30 UTC, ketmar wrote:
this is a repository name. it is supposed to be named just
"iv", and git names main directory by repository name if you
are doing a simple clone. my bad, i should have made that clear.
Ok. That helps.
On Wednesday, 26 October 2016 at 05:27:53 UTC, Jason C. Wells
wrote:
Hence the repeated advice to supply all the filenames on the
command line.
this is basically 'cause dmd doesn't automatically compile and
link imported modules. it you won't specify module in dmd command
line, dmd will only
On Wednesday, 26 October 2016 at 04:51:23 UTC, Jason C. Wells
wrote:
I am reading through Ketmar's iv.d/nanovg/package.d:
module iv.nanovg;
public import iv.nanovg.nanovg;
This looks like three levels of hierarchy, but is it?
it maps to "iv/nanovg/nanovg.d" according to dmd map rules. i
Suddenly it occurs to me that the module namespace and the
filesystem namespace do not necessarily have a one for one match,
even though they do by default. When one specifies all the D
source files on the command line, any differences between the
module namespace and the filesystem namespace a
I am reading through: https://dlang.org/spec/module.html. I'll
soon be working through a previous example provided by Mike
Parker.
I am reading through Ketmar's iv.d/nanovg/package.d:
module iv.nanovg;
public import iv.nanovg.nanovg;
This looks like three levels of hierarchy, but is it?
