From: ty AT kau1 DOT kodak DOT com (Trevor Yann)
Subject: Re: Default linker output filename
10 Nov 1996 18:58:36 -0800
Sender: daemon AT cygnus DOT com
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <1.5.4.32.19961111222031.0030cf40.cygnus.gnu-win32@mailhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Sender: ty AT mailhost
X-Mailer: Windows Eudora Light Version 1.5.4 (32)
Original-To: gnu-win32 AT cygnus DOT com
Original-Sender: owner-gnu-win32 AT cygnus DOT com

Cygwin32 could hide the filename extension for .exe files. A .exe extension
could be used for setting execute permission.

i.e.
setting a file to be executable would change the file name to include a .exe
extension.

There would be no need to modify makefiles - an output file of "foo" would
create a file called "foo", which is then marked executable, changing the
name to "foo.exe".  Using the Cygwin32 tools to view the directory
containing the file would show a file "foo" that is executable.

Opening a file would need to be modified to try for the unmodified file
name, then (if that failed), to try the name with .exe appended. Opening a
file with O_EXCL would require additional checking.

Similarly other functions that require file names might have to be modified
to look for a file with .exe extension if they can't find a file with the
unmodified name.

A side effect of this would be that marking a shell script as executable
would make it look like a binary executable.  This would only be a problem
if an attempt to execute the script was made from outside the Cygwin32
environment. 

There are problems introduced by this scheme. It is possible to create a
file "foo" and a file "foo.exe" in the same directory.


Just my 2 cents worth.

-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".