A workaround is to add .d to the command line, as it seems that
phobos makes use of deprecated stuff on windows.
Is there a bug for it already? Otherwise I could provide a fix.
--
Paulo
I'm currently working on a non-D project, and didn't yet
check if it works with DMD newer than 2.058. I
On Saturday, 28 July 2012 at 06:31:31 UTC, Jonathan M Davis wrote:
On Saturday, July 28, 2012 08:24:20 Paulo Pinto wrote:
Is there a bug for it already? Otherwise I could provide a fix.
http://d.puremagic.com/issues/show_bug.cgi?id=8003
dmd 2.060beta does not have the problem.
- Jonathan M D
On Saturday, July 28, 2012 08:24:20 Paulo Pinto wrote:
> Is there a bug for it already? Otherwise I could provide a fix.
http://d.puremagic.com/issues/show_bug.cgi?id=8003
dmd 2.060beta does not have the problem.
- Jonathan M Davis
On Saturday, 28 July 2012 at 06:01:15 UTC, Paulo Pinto wrote:
On Tuesday, 24 January 2012 at 09:45:03 UTC, Kiith-Sa wrote:
Greate news. DMD has a bug:
dmd -inline -release -O -lib -ofyaml.lib yaml.d
compile fine, but:
dmd -noboundscheck -inline -release -O -lib -ofyaml.lib yaml.d
emit errors
On Tuesday, 24 January 2012 at 09:45:03 UTC, Kiith-Sa wrote:
Greate news. DMD has a bug:
dmd -inline -release -O -lib -ofyaml.lib yaml.d
compile fine, but:
dmd -noboundscheck -inline -release -O -lib -ofyaml.lib yaml.d
emit errors.
Was it a DMD bug, or did it actually compile and cause erro
On Monday, 23 January 2012 at 19:55:11 UTC, Kiith-Sa wrote:
I've released D:YAML 0.4 . This release brings mostly updates
to keep compatibility with DMD 2.057 and bugfixes (in
particular, compilation on 32bit
works now). The constructor API has also been simplified.
Any custom YAML types (stru
On Monday, January 23, 2012 20:55:10 Kiith-Sa wrote:
> I've released D:YAML 0.4 . This release brings mostly updates to
> keep compatibility with DMD 2.057 and bugfixes (in particular,
> compilation on 32bit
> works now). The constructor API has also been simplified.
>
> Any custom YAML types (str
I added import core.stdc;
Compiles with or without it here, though, so I can't say if it
helped.
However; does that even make sense?
Shouldn't you have to import a particular module instead of just
core.stdc?
I add import core.stdc.stdlib; but core.stdc.stdlib.system(...) conflict
with std.pr
Never mind, I needed to import core.stdc.stdlib; it should work
correctly now.
I added import core.stdc;
Compiles with or without it here, though, so I can't say if it
helped.
However; does that even make sense?
Shouldn't you have to import a particular module instead of just
core.stdc?
Greate news. DMD has a bug:
dmd -inline -release -O -lib -ofyaml.lib yaml.d
compile fine, but:
dmd -noboundscheck -inline -release -O -lib -ofyaml.lib yaml.d
emit errors.
Was it a DMD bug, or did it actually compile and cause errors
when running?
I wasn't able to reproduce it, but I'm on Lin
Greate news. DMD has a bug:
dmd -inline -release -O -lib -ofyaml.lib yaml.d
compile fine, but:
dmd -noboundscheck -inline -release -O -lib -ofyaml.lib yaml.d
emit errors.
Was it a DMD bug, or did it actually compile and cause errors
when running?
I wasn't able to reproduce it, but I'm on L
I've released D:YAML 0.4 . This release brings mostly updates to
keep compatibility with DMD 2.057 and bugfixes (in particular,
compilation on 32bit
works now). The constructor API has also been simplified.
Any custom YAML types (structs and classes serialized directly
from/to YAML
nodes) now need
I've released D:YAML 0.4 . This release brings mostly updates to
keep compatibility with DMD 2.057 and bugfixes (in particular,
compilation on 32bit
works now). The constructor API has also been simplified.
Any custom YAML types (structs and classes serialized directly
from/to YAML
nodes) now
14 matches
Mail list logo
