bug-hurd
[Top][All Lists]
Advanced

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

Re: What is ``access (NULL, whatever)'' supposed to do?


From: Neal H. Walfield
Subject: Re: What is ``access (NULL, whatever)'' supposed to do?
Date: Tue, 10 Apr 2007 20:21:36 +0200
User-agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.6 (Maruoka) FLIM/1.14.6 (Marutamachi) APEL/10.6 Emacs/21.4 (i386-pc-linux-gnu) MULE/5.0 (SAKAKI)

At Tue, 10 Apr 2007 17:25:54 +0200,
<olafBuddenhagen@gmx.net> wrote:
> 
> Hi,
> 
> On Mon, Apr 09, 2007 at 10:50:26PM +0200, Thomas Schwinge wrote:
> 
> > The same happens when passing NULL file names to `open' and a lot (if
> > not all) of their friends.
> 
> Yes, that was the Qt situation.
> 
> > So, should instead `file_name_lookup' or `hurd_file_name_lookup' be
> > made robust enough to handle a NULL file name?  (Fail with EINVAL?)
> 
> Problem is that while it's easy to check for NULL, we can't easily catch
> other kinds of bad pointers. Considering this, I'm not sure it's
> worthwhile to specially handle the NULL case.

The argument is not based on helping programmers; it is based on
implementing the de facto interface for which people program.




reply via email to

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