ah that does remind me of the Amiga if copying floppys did not go well,
we used nibble-copy.
btw your surname differs 2 bytes from mine using ascii, with the same
first name (off topic this is) :)
Op 19-9-2019 om 21:23 schreef Jerry Jensen via use-livecode:
On Sep 19, 2019, at 11:53 AM, Dar
And I thought 2 bits was a quarter.
> On Sep 19, 2019, at 1:23 PM, Jerry Jensen via use-livecode
> wrote:
>
> On Sep 19, 2019, at 11:53 AM, Dar Scott Consulting via use-livecode
> wrote:
>>
>> Yeah. I love the smell of burning bytes.
>
> 4 bits is called a nybble, and
> 2 bits is called a
On Sep 19, 2019, at 11:53 AM, Dar Scott Consulting via use-livecode
wrote:
>
> Yeah. I love the smell of burning bytes.
4 bits is called a nybble, and
2 bits is called a snyf.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit
> Am 19.09.2019 um 20:53 schrieb Dar Scott Consulting via use-livecode
> :
>
> Yeah. I love the smell of burning bytes...
... in the morning. :-)
> ...
>> 'Cuz I don't even plan to use a loop if it ain't strictly called for
>> What's that smell? Oh yeah, burning bytes. :)
--
Klaus Major
Yeah. I love the smell of burning bytes.
> On Sep 19, 2019, at 12:19 PM, Curry Kenworthy via use-livecode
> wrote:
>
>
> 'Cuz I don't even plan to use a loop if it ain't strictly called for
>
> What's that smell? Oh yeah, burning bytes. :)
>
> Best wishes,
>
> Curry Kenworthy
>
> Custo
'Cuz I don't even plan to use a loop if it ain't strictly called for
What's that smell? Oh yeah, burning bytes. :)
Best wishes,
Curry Kenworthy
Custom Software Development
"Better Methods, Better Results"
LiveCode Training and Consulting
http://livecodeconsulting.com/
__
I thought of a quick way to do a first pass and it can almost fit in the margin.
> On Sep 19, 2019, at 10:25 AM, Dar Scott Consulting via use-livecode
> wrote:
>
> UTF-16 and UTF-32 are not needed in your list. Those are BE unless indicated
> otherwise by a leading BOM. That is, the BE and LE
UTF-16 and UTF-32 are not needed in your list. Those are BE unless indicated
otherwise by a leading BOM. That is, the BE and LE versions are sufficient.
ASCII encoding is a subset of CP1252, MacRoman and UTF-8, so that can be
classified as UTF-8 if there is no advantage to knowing that it is AS
I am sure my routine could be optimized some for performance. My
consideration of doing this via OSX/Windows API using LCB FFI is only
partially about performance. I think an advantage is that the OS vendors
(with way more resources than me) are more likely to keep the algorithms
reflecting up
Paul:
> I have a LiveCode Script (LCS) routine that attempts to
> follow industry common algorithms for guessing the encoding
> of a text file.
> It's performance can be slower than I would like.
Howdy,
Even though LC 9 is exceedingly slow on some operations -(cough, cough,
ahem, that's a to
I started this post of the DEV-LIST. Mark Waddingham kindly responded
and smartly suggested I should move it to the USE-LIST, so that is what
I am doing. I have also pasted Lark's reply below my original post.
-- ORIGINAL POST
I ha
11 matches
Mail list logo
