Re: Proposed nsIFile and nsILocalFile Changes - MUST READ

[Doug Turner]

Pete Collins wrote:

> > Factoring nsIFile into two pieces.
>
> Sounds like a plan. Why? Better Organization?

Simplier embedding API.

> > Removing non unicode functions.
>
> So we initialize the local file object with `initWithUnicodePath'
> instead right?

Still being debated, but it would be initWithPath()  and a unicode path would be
the parameter.

> Is there any bad things you can think of for the scripting side of
> things other than API changes?
>

None come to mind, but your the Mr. Script nsIFile.  You tell me.  :-)

> Some things i think nsIFile needs:
>
>   1. a way to unlink symlinks
>   2. a recursive copy
>   3. chown
>   4. chmod

Do you know the bug numbers?

> Remember, these `unistd' and `stat' lib calls will soon be relevant on
> the mac ;-)

cc-ing mac newsgroup:
  Good question.  With MacOS X be using the nsLocalFileUnix implementation or
the nsLocalFileMac impl?