• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Converting Xcode paths to usable paths
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Converting Xcode paths to usable paths


  • Subject: Re: Converting Xcode paths to usable paths
  • From: Jens Alfke <email@hidden>
  • Date: Tue, 1 Dec 2009 14:09:14 -0800


On Dec 1, 2009, at 1:50 PM, Steve Mills wrote:

Maybe so, but LOTS of things can't deal with them in a path.

Native file APIs aren't going to have trouble with paths like that. I can imagine that AppleScript might get confused, since it was originally written for the old Mac filesystem which had an entirely different path syntax, and got adapted to handle POSIX paths later on. Maybe they used some custom path parsing code that isn't general enough. You should probably ask about that on an AppleScript list instead of here, since Xcode isn't doing anything wrong.


—Jens

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Converting Xcode paths to usable paths (From: Steve Mills <email@hidden>)
 >Re: Converting Xcode paths to usable paths (From: Jens Alfke <email@hidden>)
 >Re: Converting Xcode paths to usable paths (From: Steve Mills <email@hidden>)

  • Prev by Date: Re: thread safety of C++ standard library
  • Next by Date: Re: Converting Xcode paths to usable paths
  • Previous by thread: Re: Converting Xcode paths to usable paths
  • Next by thread: Re: Converting Xcode paths to usable paths
  • Index(es):
    • Date
    • Thread