• Benjamin Schulte <aldoric gmx.de> May 06 2008
• Dawid Ci&#281;&#380;arkiewicz <dawid.ciezarkiewicz jabster.pl> May 06 2008
• Kevin Bealer <kevinbealer gmail.com> May 06 2008
• BCS <ao pathlink.com> May 06 2008
• Walter Bright <newshound1 digitalmars.com> May 08 2008
• terranium <spam here.lot> May 08 2008
• BCS <ao pathlink.com> May 08 2008
• Walter Bright <newshound1 digitalmars.com> May 08 2008
• BCS <ao pathlink.com> May 08 2008

Hi!
Is there a way to compile a sourcecode from stdin? It would be very helpful to
be able to compile a sourcecode from stdin direct into an object file, without
saving it first into a temporary file.

Like using
type test.d |dmd
dmd < test.d

Or is it possible with gdc?

Thanks in advance.

Benjamin Schulte Wrote:

 Hi!
 Is there a way to compile a sourcecode from stdin? It would be very helpful to
be able to compile a sourcecode from stdin direct into an object file, without
saving it first into a temporary file.
 
 Like using
 type test.d |dmd
 dmd < test.d
 
 Or is it possible with gdc?
 


On Linux (and probably some other unixes) you can try:

cat file.d | dmd /proc/self/fd/0

 Thanks in advance.


Hope this will works (haven't tried myself).

Benjamin Schulte Wrote:

 Hi!
 Is there a way to compile a sourcecode from stdin? It would be very helpful to
be able to compile a sourcecode from stdin direct into an object file, without
saving it first into a temporary file.
 
 Like using
 type test.d |dmd
 dmd < test.d
 
 Or is it possible with gdc?
 
 Thanks in advance.



The following works for me; it's a variation on what the other guy said but
provides the ".d" ending.  Also a Linux-only solution.

ln -s /proc/self/fd/0 source.d
cat actual_source.d | dmd -ofresult source.d

Note that "source" can be used by multiple dmd processes to compile different
files at the same time without conflict or synchronization, so you don't need
to create per-process objects, but of course you might need to do something
special if you want to compile multiple modules at once.

Kevin

Reply to Benjamin,

 Hi!
 Is there a way to compile a sourcecode from stdin? It would be very
 helpful to be able to compile a sourcecode from stdin direct into an
 object file, without saving it first into a temporary file.
 Like using
 type test.d |dmd
 dmd < test.d
 Or is it possible with gdc?
 
 Thanks in advance.
 


linux only as well but their might be some way to force the <(...) construct 
to be usable

Walter: any way we can get a "don't adjust the filename" flag?

BCS wrote:
 Walter: any way we can get a "don't adjust the filename" flag?


I don't know what you mean.

Walter Bright Wrote:

 BCS wrote:
 Walter: any way we can get a "don't adjust the filename" flag?


 I don't know what you mean.


maybe doing something like
dmd CONIN -ofprog.exe

Reply to Walter,

 BCS wrote:
 
 Walter: any way we can get a "don't adjust the filename" flag?
 


 


this:

dmd foo

looks for a file named "foo.d", I need to to look for "foo"

BCS wrote:
 Reply to Walter,
 
 BCS wrote:

 Walter: any way we can get a "don't adjust the filename" flag?




 this:
 
 dmd foo
 
 looks for a file named "foo.d", I need to to look for "foo"


Are you using linux or windows? Also, dmd looks at the file extension to 
see what to do with the file. .o means object file, .a means library, 
etc. Having no extension causes problems. Why not just put an extension 
on it?

Reply to Walter,

 BCS wrote:
 
 Reply to Walter,
 
 BCS wrote:
 
 Walter: any way we can get a "don't adjust the filename" flag?
 


 


 
 dmd foo
 
 looks for a file named "foo.d", I need to to look for "foo"
 




linux

 Also, dmd looks at the file extension
 to see what to do with the file. .o means object file, .a means
 library, etc. Having no extension causes problems. 


something like -iD / -iL / -iO flags would cover that. But I think that only 
source code would be used very often so making that the default would be 
reasonable in my book.

using the unix convention of - refering to stdin would cover what the OP 
wanted:

dmd -iD-

 Why not just put an extension on it?
 


Because I can't select the filename. I was trying to use the "<(command)" 
construct under bash. This replaces the given with a path to a named pipe 
that the given command's stdout can be accessed from. The name is not something 
I can effect.