On 31/01/2005 04:26 Am, John Stiles wrote:
> On Jan 31, 2005, at 5:14 PM, Mike Kluev wrote:
>
>> [The standard rant. Leading dot as a substitute for visibility
>> attribute? Extension as a substitute for type? World goes down
>> the tube :-( ]
>
> It's not really a "substitute" per se. It's just another way to hide a
> file, along with the actual invisible attribute.
> The real problem is that now it's almost impossible to figure out if
> something's hidden, or what its type/creator is, etc., unless Apple
> provides an explicit API for it. A file could be hidden in one of at
> least 3 ways now, and checking all of those ways is a huge pain. You
> can't trust the easy stuff any more—like checking the "invisible" bit
> to see if a file is invisible—since everything has Unixy "overrides"
> that could affect it as well.
Not only that. An app might find itself in a situation when it
wants to make some file visible/invisible (via the leading dot
for some specific reasons, e.g. to make Cocoa happy) but can't.
E.g. because it could mess the current FSIterator if you rename
the current item (could it?). Or because there is already a file
with the same name that has leading dot. Or just because the
name is changing and the file in question is referenced by name.
Things like that.
Keep separate things separate (good design basics 101).
Mike
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
This email sent to email@hidden
