As Julien said, there is a BC break, when a try/catch block is written
inside a loop. But I think it's not a major usage, and it's a minor
inconvenient.
Yeah, and catching and discarding exceptions also possible, albeit a minor
inconvinience.
I don't have a strong opinion on this
2013.04.24. 17:19, Dennis Clarke dcla...@blastwave.org ezt írta:
Still seeing this :
.
.
.
checking for bison version... (cached) invalid
configure: WARNING: bison versions supported for regeneration of the
Zend/PHP parsers: 1.28 1.35 1.75 1.875 2.0 2.1 2.2 2.3 2.4 2.4.1 2.4.2
2.4.3 2.5
2013.04.25. 22:01, Dennis Clarke dcla...@blastwave.org ezt írta:
The details are over at :
https://issues.apache.org/bugzilla/show_bug.cgi?id=54886
Looks to be a crash caused by php bits.
Anyone have any insights ?
--
PHP Internals - PHP Runtime Development Mailing List
To
2013/4/27 Ferenc Kovacs tyr...@gmail.com
please don't reuse the continue keyword for it.
There are a bunch of code out there where which uses exceptions in a loop
context.
For example you have a retry counter decremented in a loop and you catch
the exceptions and retry until the retry limit
Sorry but I disagree, I think you're approaching try-catch wrong.
You shouldn't have a try-catch that *can* continue on the next line after
the throw.
What you should do is have decoupled code that handles _their own
exceptions_ nicely and either cleans up after itself else it rethrows the
2013/4/27 Daniel Macedo admac...@gmail.com
Sorry but I disagree, I think you're approaching try-catch wrong.
You shouldn't have a try-catch that *can* continue on the next line after
the throw.
What you should do is have decoupled code that handles _their own
exceptions_ nicely and either
I agree with Amaury.
Although, it is rather smelly code to use try/catch as control flow
instrument, in some situations it is clearer to do it this way.
I think the new construct would be especially useful if one just wants to
log errors (no further exception handling is necessary) as shown in
