(this is related: http://forum.dlang.org/thread/jp2j66$2rdv$1@digitalmars.com, but the issue still holds)

On Tue, Apr 2, 2013 at 8:59 PM, Timothee Cour <thelastmammoth@gmail.com> wrote:
> dmd -o- does not write executable
> is this a bug or intended?
> the doc is at best confusing:
> "  -o-            do not write object file"
> if it's intended, should be: do not write object file nor executable
> Thanks,
> Timothee

On 4/3/13, Timothee Cour <thelastmammoth@gmail.com> wrote:
> dmd -o- does not write executable
> is this a bug or intended?

Intended. No object files = no way to link the executable.

Sorry but if this is the intent then dmd's help message should make this clear:

"  -o-   do not write object file"
=> "-o-  do not write object file nor executable"

>> Intended. No object files = no way to link the executable.

I was thinking in that case the object files were created in a temp location and then the executable produced in location specified by dmd's logic (-of flag or -od or current directory + file name), as is the case for dmd -run.

right now if you run :
dmd -o- -oftest test.d
it won't produce neither object nor executable, even though -of was
specified. That's extremely confusing.

On Tue, Apr 2, 2013 at 11:01 PM, Andrej Mitrovic <andrej.mitrovich@gmail.com> wrote:
> On 4/3/13, Timothee Cour <thelastmammoth@gmail.com> wrote:
>> dmd -o- does not write executable
>> is this a bug or intended?
>
> Intended. No object files = no way to link the executable.

> "  -o-   do not write object file"

By the description, I first thought of "-o-" as a way to erase the object files after linking the executable.  That would have been nice.