On Monday, 3 October 2016 at 09:06:32 UTC, Dicebot wrote:
Purpose is to skip code generation and only do syntax/semantic
validation. Very helpful when testing compiler because:
a) it takes less time speeding up overall test suite
b) doesn't require runtime static library to succeed, thus
simp
On Sunday, 2 October 2016 at 21:05:25 UTC, A D dev wrote:
One last point:
If that was always the behavior (in all versions from 2010 - or
earlier), i.e. -o- generates neither .OBJ nor .EXE, then what
is the purpose of the option? does it act as just a syntax
check?
Purpose is to skip code g
On Sunday, 2 October 2016 at 20:47:44 UTC, ag0aep6g wrote:
I think you may be misremembering things. I've checked versions
back to 2.051 (from 2010, oldest I've got lying around). None
of them wrote an executable with -o-.
1.
Thanks a lot for all that checking and for your reply.
2.
I've c
On 10/02/2016 10:33 PM, A D dev wrote:
When I compile single-file D programs, I don't want to keep the
generated object file (.OBJ, on Windows). I had checked the D compiler
options for this (using dmd --help), and IIRC, a few weeks ago, I had
used the -o- option (do not write object file) with a
Hi list,
I'm in the beginning stages of learning D. Enjoying it, but get
some issues now and then. This is one.
When I compile single-file D programs, I don't want to keep the
generated object file (.OBJ, on Windows). I had checked the D
compiler options for this (using dmd --help), and IIRC