Post #1500285
2026-04-21 18:21 UTC
I was just thinking about how Arizona Icon converted co-expressions to a pthreads implementation and suddenly realized it might be to make co-expressions ‘the’ way to get a separate thread in Icon.
But this is NOT what a co-expression is meant for! I mean, this just plain is NOT what a co-expression should be thought of as. A co-expression is a way of making an Icon generator portable and able to read messages. And thus also is best to be FAST...
#Iconlang #Icon #Unicon #ObjectIcon
Replies (1)
-
@chemoelectric@masto.ai 2026-04-21 18:27
Thus Unicon and Object Icon are the better implementations, when it comes to co-expressions. Unicon still uses stack-switching, and Object Icon uses what-I-haven’t-yet-examined. (Possible methods are numerous. One could go so far as to separately compile to C and use Cheney-on-the-MTA, or compile to GNU C and use computed goto.) If you want threads in Icon, ADD THREADS! Do it as a foreign library, if necessary.