From: pavenis AT lanet DOT lv
Message-ID: <B0000116385@stargate.astr.lu.lv>
To: djgpp-workers AT delorie DOT com
Date: Wed, 19 Jan 2000 11:56:13 +0200
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: (patch) updated protoize patch
CC: dj AT delorie DOT com
In-reply-to: <3885476F.51242B02@hmc.edu>
X-mailer: Pegasus Mail for Win32 (v3.12b)
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On 18 Jan 00, at 21:11, Nate Eldredge wrote:

> Mumit Khan wrote:
> 
> > Thanks for your comments. Since you mention that foo.c.X is not a legal
> > DOS filename, there is another one to deal with -- currently a foo.c is
> > saved as foo.c.save. I've tentatively changed that to `foo.csaved'
> > instead, which looks ugly but at least workable.
> 
> Mmm... and what do we do about foo.bar?  foo.barsaved is truncated to
> foo.bar and overwrites the original file.
> 
> foo.sav might be more reasonable.
> -- 

We'll I checked behaviour of protoize from my last build of GCC-2.95.2
I uploaded to ftp.delorie.com. Unfortunatelly I didn't do it earlier.

	DOSEMU 0.99.13 under Linux (no LFN):
		protoize doesn't work at all and is not getting far enough to
	       rename old file

		unprotoize fails to rename file. When I hexeditted exe file to
		append "_save" instead of ".save" it worked

	WIN95:
		Both protoize and unprotoize doesn't work at all (infinit loop)

So if broken protoize.exe and unprotoize.exe is problem serious 
enough, then I'll have to upload update when it will be available.

Andris