Subject: Re: Default linker output filename
From: [email-masked] (Chin Chee-Kai)

5 Nov 1996 00:20:07 -0800
Sender: [email-masked]
Approved: [email-masked]
Distribution: cygnus
Message-ID: <[email-masked]>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Authentication-Warning: gensstc.gen.co.jp: smap set sender to <[email-masked]> using -f
Original-To: Geoffrey Noer <[email-masked]>
Original-Cc: [email-masked]
In-Reply-To: <[email-masked]>
Original-Sender: [email-masked]

IMHO, if it doesn't sound too far-fetched, perhaps creating
the default output with filename "a.out" and then create
a link file "a.out.exe-->a.out" will preserve most semantics
that prep-scripts expect, and will allow human to just type
the following :
		gcc test.c
		a.out
as expected on Unix.

Chin Chee-Kai (Last, First)
Internet Email-ID:	[email-masked]
Gen Tech Corporation

> We are thinking about changing the default linker output filename from
> a.out to aout.exe.  Can anyone think of any bad consequences that might
> result?
> 
> (My gut feeling is that a.out.exe might be problematic so I lean towards
> aout.exe).

-
For help on using this list, send a message to
"[email-masked]" with one line of text: "help".