Displaying 2 results from an estimated 2 matches for "anactor".
Did you mean:
afactor
2008 Sep 30
0
[LLVMdev] Integer handling
...matched based on type).
If a match is successful then the variables of the Type matches passed
in (if no variable is specified then the Type is still matched at that
point, but nothing is set) are set to the values of those positions in
the message, so if the sender originally sent a message like:
anActor.send({"Calc", i32(18), self}); // builds a struct of { [i8 x
4], i32, {someOtherStructThatRepresentsAPid} }, which is compiled down
to a bitstream and sent out. If the receive loop above matched
something like:
{i8[4] theName, MyDataType, PID}
Then you could get what the array is as...
2008 Sep 30
2
[LLVMdev] Integer handling
OvermindDL1 wrote:
>
> It is using the Actor-Oriented model, not Object-Oriented.
> /* snip */
> By keeping the type system based on the actual types it allows
> arbitrary message passing to any other actor without needing to load
> any code relating to the actors, you can just send a structure with
> the appropriate ID and format and it will 'just work' as the