On 2014-02-16 18:09:06, Juergen Sauermann wrote:
Ad 1) I changed the assertions Symbol.cc to short warnings visible in )MORE.
I wouldn't guess to check )MORE upon getting VALUE ERROR on shared
variable, but I guess it's better than failed assertion.
Ad 3) hopefully fixed.
I've mistakenly put example X←1 under this point, but a simple scalar
of 1 is changed to 0. This is still broken in r135:
0⎕SVO'X'
1
X←1
X
0
X←2
X
2
I could further improve the shared variables for workspace-to-workspace
communication, but this is some effort and before doing it I would like to
know if someone is seriously interested in it. The idea would be a
single process
managing all shared variables and TCP rather than UDP for communication with
that process.
It appears to work correctly for cooperating users now. Malicious user,
however, can still easily destroy other users' coupling of shared variables.
I'm not going to push for changing it right now because I don't see any way
to exploit it beyond denial of service and I'm not using shared variables
for anything serious, but I think that it should be done eventually.
-k