Yeah, I've been infected too long by Unix and Windows. I forget that the old
Mac system allowed Nulls. Still, it is a very BAD idea and can frustrate the
user a lot.
On 05/02/2006 3:18 AM, "Dennis W. Manasco" <email@hidden> wrote:
> At 6:37 PM -0500 5/1/06, Keith Esau wrote:
>> Hmmm, a filename CANNOT contain a null without there being an IO error...
> Not under HFS or HFS+.
> Nulls in filenames were fairly common before OS X. I think their
> usage dated as far back as, at least, 3.2.
> Sometimes they were a part of some lame copy-protection scheme.
> Sometimes they were simply a guard against deletion. Sometimes they
> were an attempted assurance (leading null) that the item would be
> sorted first.
> Using a leading null was a standard hack for getting your extension
> to load first. Of course others did it as well...
> Norton used to report leading nulls, and I think it had a check-box
> in it's prefs specifying whether you wanted to delete them or not.
> Do not post admin requests to the list. They will be ignored.
> MPW-Dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
> This email sent to email@hidden
Do not post admin requests to the list. They will be ignored.
MPW-Dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden