Re: Why aren't large numbers limited to 64 bit values?

On Thu, Dec 10, 2015 at 1:46 PM, Peter TB Brett wrote: > When numbers are too large to represent exactly, LiveCode automatically > shifts to using 64-bit IEEE floating point representation. Floating-point > numbers store a number in three pieces: > > 1) a sign bit > 2)

LC 8 DP 11

Livecode 8 DP 11 apparently cannot be installed on Windows 7/ 32 . I tried an installation twice, both times the installation stopped (was not completed) after clicking the "Finish"-button, even after the first installation attempt I had deleted the previous DP 11 version from my machine.

Re: LC 8 DP 11

Peter, I don't think that it is a characteristic of a developer preview that an installer starts with preview 11 not to work any more. Wilhelm wasn't angry about "horrible bugs" (there will be some unsatisfying things even in the 'stable' versions of LC 7 for his great work in using LC for

Re: Probably a pointless question about using sort to search..

I haven't read everything in this thread, so I don't know if Peter's function handled this or not ... On 11/12/2015 23:32, Geoff Canyon wrote: On Thu, Dec 10, 2015 at 12:47 PM, Peter Brigham wrote: Someone on this list at some point posted an array sorting function that

Re: LC 8 DP 11

On 2015-12-11 23:30, sa...@hrz.uni-kassel.de wrote: Livecode 8 DP 11 apparently cannot be installed on Windows 7/ 32 . I tried an installation twice, both times the installation stopped (was not completed) after clicking the "Finish"-button, even after the first installation attempt I had

Re: sorting words ?

On Fri, Dec 11, 2015 at 3:28 AM, Mark Waddingham wrote: > I don't think I do agree with 'trying to do something sensible with the > whitespace' as I don't really see why that would be useful. If you break > down a string into a sequence of segments (I'll stop using word since

Re: Why aren't large numbers limited to 64 bit values?

On Thu, Dec 10, 2015 at 1:17 PM, Bob Sneidar wrote: > Because the binary equivalent of a 40 digit decimal number is NOT 40 bits. > It is many more bits. For example the binary equivalent of > 1 (17 digits) is 1010101 (27 digits). >

Re: sorting words ?

On Fri, Dec 11, 2015 at 3:28 AM, Mark Waddingham wrote: > Hehe - perhaps best not to open that particular can of worms. For what its > worth, I'd actually class that behavior as an anomaly as it breaks the > logic of string lists - if there is a trailing delimiter, the

Re: Probably a pointless question about using sort to search..

On Thu, Dec 10, 2015 at 12:47 PM, Peter Brigham wrote: > Someone on this list at some point posted an array sorting function that > might be relevant here for some applications. See below. > ​Why would anyone make a separate handler ​for this, and even more so, why make it a

Re: LC 8 DP 11

Peter, this is the sunny side of the story: If the LC 8-dp11 installer works then one can see a lot of improvements, especially in the HTML5 standalone engine and Livecode Builder. HTML5 has, TMO, now switched from 'very experimental' to 'experimental' :-)) Hermann

Re: sorting words ?

On Sat, Dec 12, 2015 at 7:24 AM, Geoff Canyon wrote: > > > I don't think I do agree with 'trying to do something sensible with the > > whitespace' as I don't really see why that would be useful. > > ​I agree that "sensible" is difficult to define here. OK, quickly off the

Re: sorting words ?

On 2015-12-11 07:56, Kay C Lan wrote: On Thu, Dec 10, 2015 at 4:38 PM, Mark Waddingham wrote: The "word" chunk is not loosely implemented - it does precisely what it is meant to do. Which of course is the reason why the sort container command has no problem if you sort

Re: Why aren't large numbers limited to 64 bit values?

Thanks, I've written a few myself. I'll post them to the forum. gc On Thu, Dec 10, 2015 at 2:09 PM, wrote: > There are handlers developed to handle numbers of any length. See the > forums. "Routines for very large numbers" > > > Craig > > > > -Original Message- > From:

Re: Probably a pointless question about using sort to search..

On Fri, Dec 11, 2015 at 6:51 PM, Alex Tweedly wrote: > > I haven't read everything in this thread, so I don't know if Peter's > function handled this or not ... > > On 11/12/2015 23:32, Geoff Canyon wrote: > >> On Thu, Dec 10, 2015 at 12:47 PM, Peter Brigham

Re: sorting words ?

On Fri, Dec 11, 2015 at 8:39 PM, Kay C Lan wrote: > 2) The List is outputted with a single space between each segment. This > would mean that if there happened to be tabs or multiple spaces between > certain segments, these would be removed/converted. This is helpful. >