Re: Do I need a newer version of Applescript (was Re: interesting discovery)
Re: Do I need a newer version of Applescript (was Re: interesting discovery)
- Subject: Re: Do I need a newer version of Applescript (was Re: interesting discovery)
- From: email@hidden
- Date: Fri, 7 Dec 2001 00:26:51 EST
In a message dated 12/6/01 10:23:57 PM, I wrote:
>
Plus, on the MacHTTP list someone said that AS 1.7 introduced a bunch of
>
new bugs (I'm about to ask which). Has anyone here heard anything?
tell chalkboard
repeat 1000
write "I will not post to the list when I have fallen behind in my
digest reading."
end repeat
end tell
I did manage to get the 9.2.2 upgrade to fully install, but I still have no
Script Editor 1.7. Should I? Very weird.
Using Script Editor 1.6 and Applescript 1.7 (and Standard Additions 1.7), I
find that
":" as alias
no longer works (as already reported). This sucks. Here is what Chris Nebel
said on Dec. 4, 2001, about this issue:
"It's the magic of relative paths. Any path starting with a colon is
considered to be relative to the current working directory. (Just a
simple name -- no colons at all -- is also considered to be relative.)
Since all you've got is the colon, you get the working directory itself,
which in traditional Mac OS is normally the folder containing the
application. (An application can change this any time it wants to, but
very few do.)
"The problem with this is that the default working directory isn't
guaranteed to be anything in particular, and is in fact different in Mac
OS X -- it's always the root of the file system. Using "path to me"
much more reliable."
No mention of removing the feature or calling it a bug, so I must assume this
newest deficiency is a bug. For me, it is a big one - every one of my CGIs
depend on it to load a script library which I conveniently place in the same
folder with the CGI. It appears that I am STILL stuck at AS1.5.5 for
production work. Thank God I never relied on writing records to text files
(did this thread just come full circle?).
"open for access" of a nonexistent file (thus creating a new file) does work
with a full path. Good. That would have been a deal killer so severe that I
would have had to run out and learn Perl.
Watch out for my coming rant (I can't eat crow and rant in the same post -
bad taste).
Jeff Baumann
email@hidden
www.linkedresources.com