[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: NSFileWrapper puzzling behavior
|
From: |
Lloyd Dupont |
|
Subject: |
Re: NSFileWrapper puzzling behavior |
|
Date: |
Fri, 2 Dec 2005 10:16:52 +1000 |
hmm.. indeed the documentation states it.. mm :-/
but it doesn't work this way (it doesn't throw any exception in fact).
well, anyway, if it's what the documentation says....
----- Original Message -----
From: "Richard Frith-Macdonald" <richard@brainstorm.co.uk>
To: "Lloyd Dupont" <lloyd@nova-mind.com>
Cc: "GNUstep Discussion" <discuss-gnustep@gnu.org>
Sent: Thursday, December 01, 2005 6:15 PM
Subject: Re: NSFileWrapper puzzling behavior
On 1 Dec 2005, at 07:28, Lloyd Dupont wrote:
Something which puzzles me:
in NSFileWrapper.m:247
if I call [aFileWrapper setFilename: nil]
that raises an exception.
what puzzles me is:
- on MacOSX it doesn't
Well, my MacOSX (Tiger) documentation explicitly states that nil (or
an empty filename0 DOES raise an exception ... so the GNUstep version
conforms to the spec.
Either you have seen a bug in MacOSX or Apple have changed things.