www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.bugs - Is this normal? dmd emptyfile.d

reply Tomás Rossi <Tomás_member pathlink.com> writes:
Is this the normal behavior of the compiler/linker?

With dmd 0.139 for Win32 and an empty file named 'test.d':
OS: Windows XP SP2

dmd test.d

OPTLINK (R) for Win32 Release 7.50B1 Copyright (C) Digital Mars 1989 - 2001 All Rights Reserved OPTLINK : Warning 23: No Stack OPTLINK : Warning 134: No Start Address The compiler/linker generates then 'test.exe' that when run creates a error message box with a description like "Error 16bit subsystem... blablabla". This occured just the first time (that's why I can't reproduce the specific error text), then the error never shows again no matter if I run again a cmd or not. Tom
Nov 11 2005
next sibling parent reply Agent Orange <no spam.com> writes:
I dunno, but what were you expecting?

Tomás Rossi wrote:
 Is this the normal behavior of the compiler/linker?
 
 With dmd 0.139 for Win32 and an empty file named 'test.d':
 OS: Windows XP SP2
 
 
dmd test.d

C:\d\dmd\bin\..\..\dm\bin\link.exe test,,,user32+kernel32/noi; OPTLINK (R) for Win32 Release 7.50B1 Copyright (C) Digital Mars 1989 - 2001 All Rights Reserved OPTLINK : Warning 23: No Stack OPTLINK : Warning 134: No Start Address The compiler/linker generates then 'test.exe' that when run creates a error message box with a description like "Error 16bit subsystem... blablabla". This occured just the first time (that's why I can't reproduce the specific error text), then the error never shows again no matter if I run again a cmd or not. Tom

Nov 11 2005
parent reply Tomás Rossi <Tomás_member pathlink.com> writes:
In article <dl3sbl$1su8$1 digitaldaemon.com>, Agent Orange says...

I dunno, but what were you expecting?

I don't know, maybe not expecting a compiler error, but perhaps linker shouldn't make an executable with no main procedure.
Tomás Rossi wrote:
 Is this the normal behavior of the compiler/linker?
 
 With dmd 0.139 for Win32 and an empty file named 'test.d':
 OS: Windows XP SP2
 
 
dmd test.d

C:\d\dmd\bin\..\..\dm\bin\link.exe test,,,user32+kernel32/noi; OPTLINK (R) for Win32 Release 7.50B1 Copyright (C) Digital Mars 1989 - 2001 All Rights Reserved OPTLINK : Warning 23: No Stack OPTLINK : Warning 134: No Start Address The compiler/linker generates then 'test.exe' that when run creates a error message box with a description like "Error 16bit subsystem... blablabla". This occured just the first time (that's why I can't reproduce the specific error text), then the error never shows again no matter if I run again a cmd or not.


Tom
Nov 12 2005
parent "Walter Bright" <newshound digitalmars.com> writes:
"Tomás Rossi" <Tomás_member pathlink.com> wrote in message
news:dl4jls$2k0f$1 digitaldaemon.com...
 I don't know, maybe not expecting a compiler error, but perhaps linker

 make an executable with no main procedure.

There are valid reasons to do that, such as building some types of specialized binary drivers.
Nov 13 2005
prev sibling parent reply Manfred Nowak <svv1999 hotmail.com> writes:
Tomás Rossi wrote:

[...]
 then the
 error never shows again no matter if I run again a cmd or not. 

Seems you compiled a D-program with no `main' routine and a subsystem of your XP-installation was faulty and automagically fixed by XP's repair mechanisms. -manfred
Nov 12 2005
parent Georg Wrede <georg.wrede nospam.org> writes:
Manfred Nowak wrote:
 Tomás Rossi wrote:
then the
error never shows again no matter if I run again a cmd or not. 

Seems you compiled a D-program with no `main' routine and a subsystem of your XP-installation was faulty and automagically fixed by XP's repair mechanisms.

Oh, man! I don't believe my eyes. 8-( Bill, some day, some day, you'll give me a heart attack. ‡-| _†_
Nov 18 2005