Re: list as string - is this a bug?
Re: list as string - is this a bug?
- Subject: Re: list as string - is this a bug?
- From: "Gary (Lists)" <email@hidden>
- Date: Thu, 08 Sep 2005 14:23:18 -0400
"Matt Neuburg" wrote:
> set L to {"hoo", "ha"}
> L as string -- "hooha"
> set L2 to {"hoo", item 2 of L}
> L2 as string -- "hooha"
> -- so far so good...
> -- but now...
> {"hoo", item 2 of L} as string -- "hoo"
>
> Huh?
That is odd, indeed.
Adding a 'get' before the lookup works as expected:
{"hoo", get item 2 of l} as string
--> "hooha"
And this explicit separation of the parts also returns the expected string:
(get {"hoo", item 2 of l}) as string
--> "hooha"
And this just sad:
{item 1 of l, item 2 of l} as string
--> ""
This must be the same kind of "look-ahead" resolution issue (feature, quirk
or bug, I don't know) as with things like 'current date' and 'info for'.
--
Gary
_______________________________________________
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