NSURL File Representation Differences

Question

applegg OP

Created Jun ’16

Replies 2

Boosts 0

Participants 2

I’m seeing two different ways the debugger represents a file URL:

Command line tool:

sourceURL NSURL *@"Comparison.mp4 -- file:///Users/gordonapple/Desktop/MetaTest/"0x0000000100500c60

My Objective C Code:

sourceURL NSURL *@"file:///Users/gordonapple/Desktop/MetaTest/Comparison.mp4"0x00006100000b5720

Is there anything of significance in the different representation here? The former works. The llatter code is not doing what I want (for whatever reason).

Boost

Answer 1

QuinceyMorris OP

Jun ’16

There should be only two slashes after the "file:" scheme.

0

Answer 2

applegg OP

Jun ’16

What I showed is what the command-line tool produces, and what comes out of the standard Open panel for the file's url.

What I was trying to get at is if the difference in these two representations in the debugger had any significance, i,e, normal linear path listing vs file name followed by directory path.

0