On Friday, 10 July 2015 at 10:22:39 UTC, anonymous wrote:
On Friday, 10 July 2015 at 00:53:38 UTC, codenstuff wrote:
On Friday, 10 July 2015 at 00:24:44 UTC, anonymous wrote:
[...]
[...]
The path is ${HOME}/d_apps/steering/steering/game_object.d
Compile command is
dmd map/map.d main_visual
On Friday, 10 July 2015 at 00:53:38 UTC, codenstuff wrote:
On Friday, 10 July 2015 at 00:24:44 UTC, anonymous wrote:
On Thursday, 9 July 2015 at 22:05:23 UTC, codenstuff wrote:
I am trying to import module and compile.
The compiler produces message
map/map.d(9): Error: module game_object is i
On Friday, 10 July 2015 at 03:11:25 UTC, Mike Parker wrote:
On Friday, 10 July 2015 at 00:53:38 UTC, codenstuff wrote:
The path is ${HOME}/d_apps/steering/steering/game_object.d
[...]
First, because you are importing sterring.game_object, then you
can't pass -I/home/real/d_apps/steering to
On Friday, 10 July 2015 at 00:53:38 UTC, codenstuff wrote:
The path is ${HOME}/d_apps/steering/steering/game_object.d
Compile command is
dmd map/map.d main_visual.d -ofmain_visual -H -gc -unittest
-L-lDgame -L-lDerelictUtil -L-lDerelictGL3 -L-lDerelictSDL2
-L-ldl -I/home/real/d_apps/dgame/so
On Friday, 10 July 2015 at 00:24:44 UTC, anonymous wrote:
On Thursday, 9 July 2015 at 22:05:23 UTC, codenstuff wrote:
I am trying to import module and compile.
The compiler produces message
map/map.d(9): Error: module game_object is in file
'steering/game_object.d' which cannot be read
impor
On Thursday, 9 July 2015 at 22:05:23 UTC, codenstuff wrote:
I am trying to import module and compile.
The compiler produces message
map/map.d(9): Error: module game_object is in file
'steering/game_object.d' which cannot be read
import path[0] = /usr/include/dmd/phobos
import path[1] = /usr/i
On Thursday, 9 July 2015 at 22:10:53 UTC, Adam D. Ruppe wrote:
The best thing to do is to pass all the modules in the project
to the compiler at once, so like:
dmd map/map.d steering/game_object.d
The import path could be changed to not include the steering/
folder - give it the folder that c
The best thing to do is to pass all the modules in the project to
the compiler at once, so like:
dmd map/map.d steering/game_object.d
The import path could be changed to not include the steering/
folder - give it the folder that contains steering - but that
still won't actually link without a
bearophile wrote:
Don:
Bug 314 is the root cause of every module bug that I know of. Basically
the compiler isn't keeping track of how symbols got imported. So it gets
everything wrong.
Bug 314 is among my voted bugs since a lot of time.
Actually it was the most voted bug in D, long befor
Don:
> Bug 314 is the root cause of every module bug that I know of. Basically
> the compiler isn't keeping track of how symbols got imported. So it gets
> everything wrong.
Bug 314 is among my voted bugs since a lot of time. Even if bug 314 isn't the
only module system bug present, solving it
bearophile wrote:
Don:
There's only really one. But it's huge.
Really? :-) I didn't know this. (You are very often right, but I have a hard
time believing this).
Bye,
bearophile
Bug 314 is the root cause of every module bug that I know of. Basically
the compiler isn't keeping track of ho
Don:
> There's only really one. But it's huge.
Really? :-) I didn't know this. (You are very often right, but I have a hard
time believing this).
Bye,
bearophile
%u wrote:
Yay, free access to a!
I searched for this bug in the bug-reports..
Why are there so many basic import bugs?
There's only really one. But it's huge.
%u:
> Why are there so many basic import bugs?
Module system bugs are among the most voted in Bugzilla. True modules are
absent in C/C++, so maybe Walter thinks assuring their semantics is correct is
not so important compared to other kinds of bugs, or maybe such bugs are hard
to fix, I don't
14 matches
Mail list logo
