Remove scary language from nsIFile target/path

RESOLVED INVALID

Status

()

RESOLVED INVALID
8 years ago
8 years ago

People

(Reporter: jduell, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

nsIFile.idl contains warnings about the native versions of path/target being potentially unsafe to pass to stdlib/NSPR function (it's silent about the non-native versions, which is confusing).

It sounds like with the demise of OS 9, we can remove the scary language and make it clear that one can safely construct a new nsIFile with a string gotten from GetPath (and also GetNativePath?  Is there a difference now?), and be guaranteed to get the same file.

Comment 1

8 years ago
These warning are correct, and have to do with Windows, not OS9. On Windows some files cannot be represented by a native path, so the only safe way to open them is with a unicode path.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.