Re: Finding \t, \r, \n reliably
Re: Finding \t, \r, \n reliably
- Subject: Re: Finding \t, \r, \n reliably
- From: Christopher Nebel <email@hidden>
- Date: Fri, 21 Oct 2005 16:53:09 -0700
On Oct 21, 2005, at 2:56 PM, Mark J. Reed wrote:
On 10/21/05, Christopher Nebel <email@hidden> wrote:
The solution is to use "ASCII character 10" (13 for a CR) instead of
the string "\n". (It's best to put that in a variable; calling
"ASCII character" repeatedly can get expensive.)
Huh. I didn't think "ASCII character" was an actual function call,
much less an expensive one. I sort of assumed that "ASCII
character 10" compiled to a literal string containing a newline.
Nope. It's a scripting addition in Standard Additions. As scripting
additions go, it's pretty cheap, but it's still more expensive than a
variable fetch.
--Chris Nebel
AppleScript and Automator Engineering
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden