Hello,
> How about just appending ".tmp" to the temp file name while
> still using ints for the pattern?
Yes, lets do this.
This is a particular case where an application depended on this bit.
The rest (the actual format of the filename) is something that we will
not copy.
Miguel
__
The only thing I cannot understand it the fact that if I submit a patch
that
corrects an MS.NET bug in Mono it is rejected or isn't welcomed altought
the
same is true for a patch that implements an MS.NET bug.
This is simply not a *fact*; it is not limited to this kind of patches.
There would
Kornél,
Hi,
How about just appending ".tmp" to the temp file name while
still using ints for the pattern?
I don't insist on 16-bit numbers if you (other people) belive that 16-bits
are few and we need 32-bits I will accept it.
But if we want to provide the same behavior as MS.NET we have t
crosoft.com/en-us/library/system.io.path.gettempfilename.aspx
Kornél
- Original Message -
From: "Robert Jordan" <[EMAIL PROTECTED]>
To:
Sent: Saturday, January 07, 2006 12:01 AM
Subject: Re: [Mono-dev] [PATCH] MS.NET compatible Path.GetTempFileName
Kornél,
The only thing I cannot understand it the fa
Kornél,
The only thing I cannot understand it the fact that if I submit a patch
that
corrects an MS.NET bug in Mono it is rejected or isn't welcomed altought
the
same is true for a patch that implements an MS.NET bug.
Well, in your first mail you did't explain why on earth mono
have to mimic
quot;Ben Maurer" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc:
Sent: Friday, January 06, 2006 8:44 PM
Subject: Re: [Mono-dev] [PATCH] MS.NET compatible Path.GetTempFileName
MS.NET uses Windows API GetTempFileName function for
Path.GetTempFileName. If we want full compatibility
> MS.NET uses Windows API GetTempFileName function for
> Path.GetTempFileName. If we want full compatibility we should implement
> it in the I/O layer using a global unsigned 16-bit counter that starts
> from zero and is incremented without overflow check each time
> GetTempFileName is called.
I h
