ruby-x/ruby-x.github.io
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

removed callee, using receier

Browse Source
This commit is contained in:
Torsten Ruger 2014-07-17 00:54:36 +03:00
parent 5eddfec928
commit 6ef7ef0572
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
_posts/2014-07-17-framing.md
View File

@ -48,7 +48,7 @@ constant.
And as a final bonus of all this clarity, i immediately spotted the inconcistency in my oen design: The frame i designed And as a final bonus of all this clarity, i immediately spotted the inconcistency in my oen design: The frame i designed
holds local variables, but the caller needs to create it. The caller can not possibly know the number of local variables holds local variables, but the caller needs to create it. The caller can not possibly know the number of local variables
as that is decided by the invoked method, which is only known at run-time. So we clearly need a two level thing here, one as that is decided by the invoked method, which is only known at run-time. So we clearly need a two level thing here, one
that the caller creates, and one that the callee creates. that the caller creates, and one that the receiver creates.
### Messaging and slots ### Messaging and slots

2
crystal/optimisations.md
View File

@ -81,5 +81,5 @@ This only really makes sense if the register shuffling information is encoded in
to be passed). to be passed).
Negotiators could do some counting and do the recompiling when it seems worth it. The Negotiator would remove itself from Negotiators could do some counting and do the recompiling when it seems worth it. The Negotiator would remove itself from
the chain and connect called and new callee directly. How much is in this i couldn't say though. the chain and connect called and new receiver directly. How much is in this i couldn't say though.