You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now we have the capability to run opcodes that manipulate registers and constant input, functional blocks should be made to allow for methods, anonymous functions etc. The notion of scope beyond the local scope (well defined by a register group) could be fun here.
The text was updated successfully, but these errors were encountered:
The easy route may well be to extend the Executor, to allow it to also be an opcode in it's own right. This will offer a very interesting property, if the assumption is Executors can be operated like threads, in that any function defined may also be multi-threaded in execution, with no notion of intrinsically locking the object it's associated with.
A part of this (and something of a requirement for anonymous functions anyway) would be the ability to hold a function reference in a register. This could however be managed by anonymous objects, referenced by registered instead.
Now we have the capability to run opcodes that manipulate registers and constant input, functional blocks should be made to allow for methods, anonymous functions etc. The notion of scope beyond the local scope (well defined by a register group) could be fun here.
The text was updated successfully, but these errors were encountered: