On Jan 14, 2000, "Edouard G. Parmelan" <[EMAIL PROTECTED]> wrote:
> Alexandre Oliva wrote:
>> BTW, waitpid doesn't load pid either :-(
> Okay, I will fix that too
Thanks
--
Alexandre Oliva http://www.ic.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
oliva@{lsd.ic.unicamp.br,guarana.{org,com}} aoli
Alexandre Oliva wrote:
> > I see, pid is not saved after fork.
> > Fixed now, thanks.
>
> BTW, waitpid doesn't load pid either :-(
Okay, I will fix that too, but I have to check KWAITPID() also. For
exemple in unix-jthread(), it loop on error (with a comment) but on
BeOS, it return the error
On Jan 14, 2000, "Edouard G. Parmelan" <[EMAIL PROTECTED]> wrote:
> I see, pid is not saved after fork.
> Fixed now, thanks.
BTW, waitpid doesn't load pid either :-(
--
Alexandre Oliva http://www.ic.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
oliva@{lsd.ic.unicamp.br,guarana.{org,com}} aoliva@{ac
Mike Linksvayer wrote:
> 3. I had assumed that cvs diff would give me differences between
> the head revision and my file, but apparently it gives the differences
> between the revision I have checked out and my file ... I haven't
> used cvs in two years. :(
Yes, ``cvs diff foo'' report diff b
On Thu, Jan 13, 2000 at 02:37:13PM -0500, Mike Linksvayer wrote:
> Argh, please unfix. I'm an idiot ... the behavior of getAbsolutePath()
> is correct, only getCanonicalPath() is incorrect. I'll post a real
> fix tonight, after I've tested more thoroughly.
It happens that getCanonicalPath was
Mike Linksvayer writes:
> > Thanks, fixed!
>
> Argh, please unfix. I'm an idiot ... the behavior of getAbsolutePath()
> is correct, only getCanonicalPath() is incorrect. I'll post a real
> fix tonight, after I've tested more thoroughly.
OK, unfixed! :-)
-Archie
_
> Thanks, fixed!
Argh, please unfix. I'm an idiot ... the behavior of getAbsolutePath()
is correct, only getCanonicalPath() is incorrect. I'll post a real
fix tonight, after I've tested more thoroughly.
I must learn not to:
* think code is finished before writing unit tests
* think code is fi
Mike Linksvayer writes:
> File.getAbsolutePath() was not stripping out extra "." path
> components, which is contrary to the behavior of the JDK, and
> breaks user code that relies on the JDK behavior. getCanonicalPath()
> was also broken was a result.
>
> The following code produces a simple c
File.getAbsolutePath() was not stripping out extra "." path
components, which is contrary to the behavior of the JDK, and
breaks user code that relies on the JDK behavior. getCanonicalPath()
was also broken was a result.
The following code produces a simple case:
System.err.println(new
