Re: Understanding a repeat loop (strings/characters)
Re: Understanding a repeat loop (strings/characters)
- Subject: Re: Understanding a repeat loop (strings/characters)
- From: has <email@hidden>
- Date: Mon, 24 Feb 2003 05:02:58 +0000
Steven Angier wrote:
>> It is a shame that 'item' is not synonymous with 'text item'.
It would certainly add a bit more flexibility in what you could do
within the existing structures. But the character=item relationship
is more logical (e.g. both are atomic; also, how would a loop cope if
TIDs changed midway?) so I think it was the right choice. Whereas I
could run off a list of faults with AS's TIDs. (I know which I'd
rather see gone.)
As I am sure Has and others will attest to, I don't consider the ability to
get an "item" of a string (returning a character) a feature. Again, because
it exposes the ugliness of C strings.
Only because you 'think' in C, and then apply that thinking to
something not remotely C-like. :)
Me, I think in object-oriented terms, so to me this behaviour makes
total sense and is a very solid, smart and elegant bit of design. [1]
BTW, it doesn't expose any actual implementation details, so any
apparent similarities are purely superficial. (Note, for example,
that the unicode text type employs the same properties and elements
as the string type, and you certainly couldn't accuse that of being
'C character array-like'.)
has
[1] But don't feel too bad - l33t OO sk1llz aren't everything, and
left alone in C I'd be killed and eaten by rampaging mallocs in
seconds.
--
http://www.barple.pwp.blueyonder.co.uk -- The Little Page of AppleScripts
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.