Re: evalhate without parsing?
Re: evalhate without parsing?
- Subject: Re: evalhate without parsing?
- From: Christopher Nebel <email@hidden>
- Date: Tue, 07 May 2013 11:21:41 -0700
To be more explicit, see "numeric strings" under that URL:
considering / ignoring (text comparison)
...
numeric strings
By default, this attribute is ignored, and text strings are compared according to their character values. For example, if this attribute is considered, "1.10.1" > "1.9.4" evaluates as true; otherwise it evaluates asfalse. This can be useful in comparing version strings.
If the surrounding content is the same for both strings, that comparison option is all you need.
--Chris Nebel
AppleScript Engineering
On May 2, 2013, at 3:11 PM, Philip Ershler <email@hidden> wrote:
> Comparing strings for less than or greater than can get to be a very messy business, particularly if they characters are unicode. See this URL
>
> https://developer.apple.com/library/mac/#documentation/applescript/conceptual/applescriptlangguide/reference/ASLR_control_statements.html
>
> Phil
>
> On May 2, 2013, at 4:05 PM, Christopher Stone <email@hidden> wrote:
>
>> On May 02, 2013, at 16:50, Robert Poland <email@hidden> wrote:
>>> My point is that comparing LIKE strings with embedded UNLIKE numbers seem to respond to the embedded numbers.
>> ______________________________________________________________________
>>
>> Hey Bob,
>>
>> Well. That can be dangerous, because the numbers are not the things being compared.
>>
>> In this particular case it's probably safe because of the way the characters are stacked.
>>
>> But if Smile goes into the double-digits there could be problems:
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden