On Sat, Aug 4, 2012 at 12:47 AM, Stas Malyshev wrote:
> Hi!
>
>> I'm looking at a segfault in the SPL caused by the blind creation of a
>> class, which seems to only fail when the class is disabled. I'm
>> wondering in how many other places this could occur.
>
> This seems to be pretty bad. I'd sa
Hi!
> I'm looking at a segfault in the SPL caused by the blind creation of a
> class, which seems to only fail when the class is disabled. I'm
> wondering in how many other places this could occur.
This seems to be pretty bad. I'd say creation of an instance of disabled
class should be a fatal er
Which brings up the issues that I mentioned before.
Getting the return of an erroring function isn't such a big issue, but
turning everything into exceptions would prevent getting any return value from
any function/operation which triggers anything,
Maybe you want to keep your cake and eat
a php function/operation can raise more than one warning, how would you
handle that?
with exceptions you would only get the first one.
another issue is that with the current error handling model a call can
trigger a non-fatal error and still return some data.
with exeptions you can't do
On 03/08/12 17:04, Ferenc Kovacs wrote:
Warnings are special, they aren't really errors as such. They
wouldn't become exceptions.
Also, why should an erroring function return a value?
from
"My experience shows it's best to have an error handler convert all
errors to catchable ex
>
>
>> Warnings are special, they aren't really errors as such. They wouldn't
> become exceptions.
>
> Also, why should an erroring function return a value?
>
>
from
"My experience shows it's best to have an error handler convert all errors
to catchable exceptions, with some error types (like E_ST
On 03/08/12 16:50, Ferenc Kovacs wrote:
On Fri, Aug 3, 2012 at 4:19 PM, Stan Vass wrote:
Hi all,
Can anyone explain to me the reason that when a function or class is
disabled via the ini setting, an attempt to access the disabled item
generates a non-fatal error?
I'm looking at a segfault in
On Fri, Aug 3, 2012 at 4:19 PM, Stan Vass wrote:
> Hi all,
>>
>> Can anyone explain to me the reason that when a function or class is
>> disabled via the ini setting, an attempt to access the disabled item
>> generates a non-fatal error?
>>
>> I'm looking at a segfault in the SPL caused by the bl
On Fri, Aug 3, 2012 at 3:08 PM, Leigh wrote:
> Hi all,
>
> Can anyone explain to me the reason that when a function or class is
> disabled via the ini setting, an attempt to access the disabled item
> generates a non-fatal error?
>
> I'm looking at a segfault in the SPL caused by the blind creatio
Hi all,
Can anyone explain to me the reason that when a function or class is
disabled via the ini setting, an attempt to access the disabled item
generates a non-fatal error?
I'm looking at a segfault in the SPL caused by the blind creation of a
class, which seems to only fail when the class is
On Fri, Aug 3, 2012 at 1:59 PM, Leigh wrote:
>> Because there isn't anything actually wrong.
>>
>> A fatal error is reserved for things we cannot recover from, but a
>> disabled function is easily recoverable.
Another great use-case for engine-thrown exceptions.
IMHO we should really rethink the
> Because there isn't anything actually wrong.
>
> A fatal error is reserved for things we cannot recover from, but a
> disabled function is easily recoverable.
I don't see how it is any more recoverable than the function/class not
existing at all. How much code do you know of that checks for the
On Fri, Aug 3, 2012 at 8:08 AM, Leigh wrote:
> Hi all,
>
> Can anyone explain to me the reason that when a function or class is
> disabled via the ini setting, an attempt to access the disabled item
> generates a non-fatal error?
Because there isn't anything actually wrong.
A fatal error is rese
Hi all,
Can anyone explain to me the reason that when a function or class is
disabled via the ini setting, an attempt to access the disabled item
generates a non-fatal error?
I'm looking at a segfault in the SPL caused by the blind creation of a
class, which seems to only fail when the class is d
14 matches
Mail list logo
