Anything LiveCode Can Learn From GO

Ralph DiMola rdimola at
Thu Jun 14 11:24:07 EDT 2018

I would love to be able to start a thread that formatted a field that might be selected and made visible at a later date or have a scrolling field that could have the non-visible lines being formatted in another thread before you scroll down. Say you were going to a new card that required a DB query. You could have the card layout code and the query to a local DB running at the same time. Even with LCs message hierarchy multithreading could work. You could fire off a DB query thread and have a message sent to the main thread when complete. Inter thread communication would be key. That is where locking would be tricky to prevent dead locks.

Ralph DiMola
IT Director
Evergreen Information Services
rdimola at

-----Original Message-----
From: use-livecode [mailto:use-livecode-bounces at] On Behalf Of Bob Sneidar via use-livecode
Sent: Thursday, June 14, 2018 10:56 AM
To: How to use LiveCode
Cc: Bob Sneidar
Subject: Re: Anything LiveCode Can Learn From GO

Multithreading sounds like a good idea until you realize most things that have to happen in Livecode due to the message heirarchy need to be single threaded. It's only when you need to make a server of some sort that multithreading really needs to be implemented. 

Bob S

> On Jun 11, 2018, at 17:08 , Sannyasin Brahmanathaswami via use-livecode <use-livecode at> wrote:
> I wasn't thinking about high language per se.   but more from an engine point of view, specifically use of "Goroutines"
> "But, most of the modern programming languages(like Java, Python etc.) are from the ’90s single threaded environment. Most of those programming languages supports multi-threading. But the real problem comes with concurrent execution, threading-locking, race conditions and deadlocks. Those things make it hard to create a multi-threading application on those languages.

use-livecode mailing list
use-livecode at
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

More information about the Use-livecode mailing list