Re: Producing Unicode-only characters [was: Finding \t, \r, \n reliably]
Re: Producing Unicode-only characters [was: Finding \t, \r, \n reliably]
- Subject: Re: Producing Unicode-only characters [was: Finding \t, \r, \n reliably]
- From: Emmanuel <email@hidden>
- Date: Wed, 26 Oct 2005 10:53:04 +0200
At 8:30 AM +1000 10/26/05, Shane Stanley wrote:
On 26/10/05 5:36 AM, "Christopher Nebel" <email@hidden> wrote:
the major "downside" is simply that it doesn't do what
(I thought) Shane was asking for, which was to convert from the
character to the code point at run-time.
Right. I guess I'm asking (pleading?) for a simple equivalent to ASCII
character and ASCII number, but hopefully capable of dealing in strings
rather than a character at a time (thereby ruling out "simple", I guess).
Shane, it's a pity you can't afford using Smile. You would waste less
time asking (pleading?) for new built-in features.
Logically, you should not too often ask the AppleScript team to
implement a new feature that a third-party programmer could implement.
If they follow your suggestion, they will take on the time they would
otherwise spend on the issues that no-one can program for them, so
your suggestion will slow down the improvements of the language.
This seems particularly a sensible advice about features *already
correctly implemented*, which is the case here.
One of the powerful ideas in AppleScript is that Apple program a core
not too heavy to maintain, and since it's a communication language
third-party programmers provide the commands that users need. I would
think that as a user who appreciates AppleScript you should share and
even favor this vision.
Emmanuel
_______________________________________________
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