rfc:ripples
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| rfc:ripples [2013/10/30 10:49] – [Proposal] krakjoe | rfc:ripples [2013/10/30 10:53] – [Proposal] krakjoe | ||
|---|---|---|---|
| Line 90: | Line 90: | ||
| <code php> | <code php> | ||
| /* ... */ | /* ... */ | ||
| - | drop new SocketReadRipple($socket); | + | drop new SocketReadRipple($this); |
| /* ... */ | /* ... */ | ||
| </ | </ | ||
| Line 96: | Line 96: | ||
| The flow of this program could be described as fragmented, but it is //not// broken, execution //flows// from one block to another in a non-linear way. | The flow of this program could be described as fragmented, but it is //not// broken, execution //flows// from one block to another in a non-linear way. | ||
| - | Instead of throwing exceptions to be caught, unconditionally altering the flow of execution, we can drop ripples to be dammed allowing execution to recover. | + | Instead of throwing exceptions to be caught, unconditionally altering the flow of execution, we can drop ripples to be dammed, allowing execution to recover. |
| ===== Backward Incompatible Changes ===== | ===== Backward Incompatible Changes ===== | ||
rfc/ripples.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1