Mail Archives: cygwin/1996/11/04/22:49:22
Wade Richards taps on the keyboard:
>
> I would suggest a.out.exe. In my opinion, the only reason to leave it
> anything like the UNIX standard, a.out, is for compatability. In this case,
> close is not close enough. If some program (say, a "configure" script)
> compilies code and expects to run "a.out", it won't find "aout.exe", no
> matter how close you think the name is. On the other hand, if there is a
> file called "a.out.exe", and your script executes "a.out", it will work.
Well, I've done some testing and Win95 in the command prompt won't
recognize a.out.exe as a valid executable when I type ".\a.out".
Since the only reason to change the default exec name is for Win 95
compatibility, a.out.exe is out as an option I think.
Time to find out just how many configury things break with "a.exe"
I think...
--
Geoffrey Noer
noer AT cygnus DOT com
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".
- Raw text -