[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Lynx-dev] Re: Standards compliance..? (Was Re: non-pkgsrc emacs or clon

From: David Maxwell
Subject: [Lynx-dev] Re: Standards compliance..? (Was Re: non-pkgsrc emacs or clone)
Date: Wed, 25 May 2005 15:44:39 -0400
User-agent: Mutt/

On Wed, May 25, 2005 at 11:07:37AM -0700, Marc Tooley wrote:
> On Wednesday 25 May 2005 08:59, Todd Vierling wrote:
> > Please keep your (likely Linux-advocacy based) flamebait at home. 
> > The rest of us are working with third party software quite
> > successfully on NetBSD, and it's unfortunate that you feel the need
> > to have an unfounded temper tantrum about it.
> I'm pretty sure there was a NetBSD commit to fix mkdir() (and other 
> calls) so they worked with a trailing slash, in violation of the Single 
> UNIX Standard which states that all trailing slashes must be 
> interpreted as "/." everywhere. Many applications made assumptions 
> about it apparently, because it "just worked" on so many other 
> platforms.

Nope. The SUS didn't specify the behaviour in the case of mkdir, because
the argument to mkdir(2) is not (yet) a directory, it's a name for which
you wish to create a directory.

So, the decision was easy to make - compatibility, given that no
standard had to be violated.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]