Re: path to as string
Re: path to as string
- Subject: Re: path to as string
- From: Christopher Nebel <email@hidden>
- Date: Mon, 27 Jun 2005 16:26:47 -0700
On Jun 27, 2005, at 12:33 PM, has wrote:
Christopher Nebel wrote:
<http://www.apple.com/applescript/releasenotes/192OSX.html>
<http://developer.apple.com/documentation/Carbon/Reference/
Apple_Event_Manager/apple_event_manager_ref/
chapter_1.4_section_96.html>
"Deprecated" in Apple documentation usually implies that the
function/
constant/whatever in question is going to completely disappear
sometime soon-ish. This is not the case with typeText and friends,
The above links indicate otherwise; might want to fix that.
Sigh. Okay, apparently I don't (or didn't) understand what
"deprecated" means either, since I think I wrote the release note,
but one of our documentation staff wrote the reference document. The
practical upshot is that typePString and typeCString are "deprecated"
as in "quit using them now, because they're going to disappear from
the headers in a release or two"; typeText, typeStyledText, etc. are
"not recommended" as in "they'll stick around, but have inherent
limitations that will screw you in certain environments, so use them
at your peril." I'll see about making the documents consistent.
If you have a stream of bytes that somehow defines its own encoding,
it's technically not text, but merely data, and you should use
typeRawData for it.
Not familiar with that one; where's it defined?
Wow, I seem to have hallucinated that one based on the "raw data"
type in AppleScript. OK, maybe it doesn't exist, in which case it
should.
Having an off day,
--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