On 20/01/2023 18:26, Geoff Canyon via use-livecode wrote:
I'm sure someone has done the work to create a more efficient algorithm for
this. Off the top of my head if I were trying to I'd probably do something
like:
Hmmm. Maybe. But I kind of doubt it (though I'd love to find out I'm wrong).
Duh. What part of Sod's Law says that you always see a bug the first
time you look at your own code *after* you've made the code public :-(
The 'sort' command below needs to be a numeric sort
sort pLines by item 1 of each -> sort pLines numeric by item 1
of each
Sorry,
Alex.
I'm sure someone has done the work to create a more efficient algorithm for
this. Off the top of my head if I were trying to I'd probably do something
like:
1. Grab two points at random (in case the points are pre-sorted in some
way) and get the distance.
2. Assume that's a reasonable average
Whoa, TIL. Of course ChatGPT was easily able to make the substitution. I've
updated the doc.
gc
On Fri, Jan 20, 2023 at 9:46 AM Alex Tweedly via use-livecode <
use-livecode@lists.runrev.com> wrote:
> On 20/01/2023 15:55, Geoff Canyon via use-livecode wrote:
>
> > Responses inline:
> >
> > On
On 20/01/2023 16:52, Mark Waddingham via use-livecode wrote:
On 2023-01-20 13:05, Alex Tweedly via use-livecode wrote:
We need a better algorithm. If we use a "linear scan", we can change
it from essentially Order(N**2) to approx Order(N).
Slightly pedantic point (I appreciate that you did
On 20/01/2023 15:55, Geoff Canyon via use-livecode wrote:
Responses inline:
On Fri, Jan 20, 2023 at 5:06 AM Alex Tweedly via use-livecode <
use-livecode@lists.runrev.com> wrote:
I thought of this -- especially since ChatGPT's first (python-esque)
example uses "inf" -- but what would you use
On 2023-01-20 13:05, Alex Tweedly via use-livecode wrote:
We need a better algorithm. If we use a "linear scan", we can change
it from essentially Order(N**2) to approx Order(N).
Slightly pedantic point (I appreciate that you did say 'approx')...
Sorting can not be done in any less time than
Doomed, like the guys who left their weapons behind ended up facing their own
weapons later.
Bob S
On Jan 20, 2023, at 07:56 , Geoff Canyon via use-livecode
mailto:use-livecode@lists.runrev.com>> wrote:
On Fri, Jan 20, 2023 at 6:57 AM Craig Newman via use-livecode <
On Fri, Jan 20, 2023 at 6:57 AM Craig Newman via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Geoff.
>
> Startling, and beautifully presented.
>
> I had no idea ChatGPT was that powerful and knowledgeable.
>
> We are doomed.
>
> Craig
>
Doomed like the guys walking behind the horses
Responses inline:
On Fri, Jan 20, 2023 at 5:06 AM Alex Tweedly via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Fascinating. Thank you so much for that Geoff.
>
> I've been afraid to play with ChatGPT so far - too worried abut getting
> sucked in and spending way too much time
>
>
Geoff.
Startling, and beautifully presented.
I had no idea ChatGPT was that powerful and knowledgeable.
We are doomed.
Craig
> On Jan 20, 2023, at 8:05 AM, Alex Tweedly via use-livecode
> wrote:
>
> Fascinating. Thank you so much for that Geoff.
>
> I've been afraid to play with ChatGPT
Fascinating. Thank you so much for that Geoff.
I've been afraid to play with ChatGPT so far - too worried abut getting
sucked in and spending way too much time
I did take a look at your third example (since I can never resist a
performance challenge :-)
There are a number of minor
Geoff...
Wow. Pretty please, can I have permission to turn that document into a blog
post? It's fantastic and deserves to reach a wider audience.
Best Regards,
Heather
Heather Laine
Customer Services Manager
LiveCode Ltd
www.livecode.com
> On 20 Jan 2023, at 06:02, Geoff Canyon via
I tested three use cases, with variations, using ChatGPT for (live)code
generation. There was a lot of back and forth. In the end, I solved all the
problems I set, but in some cases I had to hold ChatGPT's hand pretty
tightly.
That said, I learned some things as well -- about LiveCode. ChatGPT's
14 matches
Mail list logo
