Re: TIDs case insensitive?
Re: TIDs case insensitive?
- Subject: Re: TIDs case insensitive?
- From: Nigel Garvey <email@hidden>
- Date: Fri, 9 Mar 2001 11:29:21 +0000
Chris Nebel wrote on Thu, 08 Mar 2001 16:32:30 -0800:
>
Arthur J Knapp wrote:
>
>
> Just to add my two cents, I kind of think that a larger issue
>
> is being skirted around here. The incentive to add functionality
>
> to the text item delimiters is based upon the fact that so many
>
> of us rely upon them as a work-around for the lack of proper
>
> string commands.
Just to add my 1.25p (I'm afraid haven't seen today's exchange rate), I'd
like to see the TID's made less of a production number and less permanent
in scope. For instance, they could be used as individual command
parameters (as with the 'read' command) instead of being long-windedly
set until reset. This would also (in theory) lessen the effort of
resetting them should anything go wrong while they're at non-default
values.
set fred to text items of pathString using delimiters {":"}
And/or perhaps they could have their own scope blocks:
using delimiters{":"}
set fred to text items of pathString
... blah blah blah ...
end using
>
P.S.: Sorry about the doubled post earlier, but I didn't see the first one
>
come
>
through until today. In fact, I still seem to be stuck in some sort of time
>
warp -- I'm getting a bunch of applescript-users messages dated Wednesday.
>
Is
>
anyone else seeing this?
That's just one of the things we digest readers have known about for
ages. ;-)
NG