Agemixer (14:32:14)
but to make the scheduler work properly, it swaps so many bytes in memory, it will be sluggish, and quite inefficient even. The less i/o or vars area is required in "code and debug" process side, the less swapping is needed, the better efficiency.

Agemixer (14:25:31)
while the another "process" is executing the actual basic program..

Agemixer (14:21:21)
one can add some debug program of BASIC code lines, printing out variables in a loop

Agemixer (14:19:22)
mirrorbird: IPC Hmm, it is uust within same memory areas and pointers anyway, so, variables should be possible to read, just with a print command

mirrorbird (10:29:39)
you had too many pulls on the asynchronous crack pipe

zoi (10:00:38)
it must've been 20 years since I was benchmarking the meteorological institutues new cluster with some IPC

zoi (10:00:02)
is that the same IPC as it was back in the day?

Agemixer (09:37:47)
just if the basic lines ate modified, added or removed anyhow, all executions must stop at that point and update all possible pointers and running variables before continuing the program exe

mirrorbird (09:37:21)
+ reserve a little RAM for IPC

Agemixer (09:35:32)
mirrorbird: thinking out loud in fact i guess, in fact, it makes sense to share most the same areas and use full available RAM etc, except that another instance of BASIC could be used for programming WHILE executing that basic program in another

A Final Hyperbase - Enigma [remix]

Ini (Stanisław Ostaszewski)

zeograd

Time Left: 5:37