rfc:ripples
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
rfc:ripples [2013/10/30 10:49] – [Proposal] krakjoe | rfc:ripples [2017/09/22 13:28] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 69: | Line 69: | ||
try { | try { | ||
- | while (($buffer = $socket-> | + | while (($buffer = $transcoder-> |
} | } | ||
- | } catch (SocketTranscodeException | + | } catch (DataDecodeException |
/* this is exceptional */ | /* this is exceptional */ | ||
/* nothing can be done to recover execution */ | /* nothing can be done to recover execution */ | ||
} | } | ||
- | } dam (SocketReadRipple $sex) { | + | } dam (SocketReadRipple $sr) { |
} | } | ||
} | } | ||
- | } dam (SocketDisconnectRipple $se) { | + | } dam (SocketDisconnectRipple $sd) { |
} | } | ||
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 | + | We throw 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 ===== | ||
Line 133: | Line 133: | ||
Do we have in ripples a viable replacement for warnings and notices ? | Do we have in ripples a viable replacement for warnings and notices ? | ||
- | ===== Proposed Voting Choices | + | ===== Preempted Opinions |
* You are crazy | * You are crazy |
rfc/ripples.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1