2013/4/26 Andreas Heigl
> try {
> $foo = $bar->getObject();
> $foo->doSomething()
> } catch(Exception $e) {
> continue // Or whatever shall be used
> }
>
> When $bar->getObject throws an Exception no $foo is set. So the next
> line will result in a "PHP Fatal error: Call to a member
I like the idea but would prefer another control structure such as
CreateTryCatchBlockForEverySingleLine (should be shorter though) rather than
continue.
The continue keyword is confusing in my opinion. And I would say it should
be for every single statement whereupon a statement is defined by eit
Am 26.04.13 16:41, schrieb Julien Pauli:
> Hello internals,
>
> I had an idea recently with a friend, about a feature try-catch blocks
> could use.
> Let me just write an example, you will quickly understand the idea :
>
> * *
> *
> *try {*
> * foo();*
> * bar();*
> * baz();*
> *} catch (So
Ola,
my name is Guilherme Capilé, I'm a Brazilian developer and I'd like to
contribute to the PHP-SRC. Right now, specifically to the PDO DBLIB
(ext/pdo_dblib) extension. I've already submitted a bug, a patch and a
pull request, a month ago, but haven't got any responses so far --
looks like no on
Access to the most current industry news and information including:
- Over 47,000 detailed celebrity profiles
- Box office scores
- Complete agency and management rosters
- Responsible and Territorial agents
- Performance fees, production information, artist bios
- Record company profiles, CD rel
Hi
2013/4/26 Lazare Inepologlou :
> This seems like a BC break:
>
> for ( ; ; ) {
> try {
> ...
> } catch (Exception $e) {
> continue;
> }
> }
>
> With the proposed syntax, "continue" will no longer refer to the "for" loop.
Well, at the moment "continue" is assigned to only usage i
I will answer, as the idea came from Pierrick Charron and I :-)
Sometimes, you call functions (or methods) and you know they can throw some
exceptions. But you don't want to stop all computations just because one of
them raised an exception. Maybe you just want to log it, and go to the next
call.
On Friday 26 April 2013 16:41:17 Julien Pauli wrote:
> *try {*
> * foo();*
> * bar();*
> * baz();*
> *} catch (SomeException $e) {*
> *dosomestuff();*
> *continue; /* Here is the feature, go back to try block */*
> *} catch (Exception $e) {*
> *dosomething();*
> *}*
>...
> So, i
2013/4/26 Julien Pauli
> Hello internals,
>
> I had an idea recently with a friend, about a feature try-catch blocks
> could use.
> Let me just write an example, you will quickly understand the idea :
>
> * *
> *
> *try {*
> * foo();*
> * bar();*
> * baz();*
> *} catch (SomeException $e) {*
Sounds interesting. And what about the second attempt passing the try block
without goto?
2013/4/26 Julien Pauli
> Hello internals,
>
> I had an idea recently with a friend, about a feature try-catch blocks
> could use.
> Let me just write an example, you will quickly understand the idea :
>
>
Hello internals,
I had an idea recently with a friend, about a feature try-catch blocks
could use.
Let me just write an example, you will quickly understand the idea :
*
On 2013-04-25, Stas Malyshev wrote:
> Hi!
>
>> Shouldn't we
>>
>> Keep CURL_WRAPPERS_ENABLED defined to 0 ?
>>
>> or remove it from PHP-5.4 before 5.4.15 ?
>> (was not included in any "official" version yet)
>
> Since the wrappers are gone, I think we should just drop it. If I don't
> hear any o
12 matches
Mail list logo
