What do you mean?
Regards,
Michael
On 8/10/06, Marcus Boerger <[EMAIL PROTECTED]> wrote:
Hello Michael,
hwat are you doing there? You turn any new oop feature as oh php 5 into a
joke. What do you aim at?
Thursday, August 10, 2006, 12:02:09 PM, you wrote:
> Hi,
> right now, PHP triggers
Hello Michael,
this is the expected behavior. But we migth as well simply remove all
those modifiers. That would be much better then providing them in a
senseless manner.
regards
marcus
Thursday, August 10, 2006, 12:02:09 PM, you wrote:
> Hi,
> right now, PHP triggers fatal errors e.g. when
Hello,
On 8/10/06, Derick Rethans <[EMAIL PROTECTED]> wrote:
On Thu, 10 Aug 2006, Ilia Alshanetsky wrote:
>
> On 10-Aug-06, at 9:35 AM, Michael Walter wrote:
>
> > What do you feel is incorrect about allowing mentioned errors to be
> > handled in userspace?
>
> My feeling is that errors such as
On Thu, 10 Aug 2006, Ilia Alshanetsky wrote:
>
> On 10-Aug-06, at 9:35 AM, Michael Walter wrote:
>
> > What do you feel is incorrect about allowing mentioned errors to be
> > handled in userspace?
>
> My feeling is that errors such as visibility violations should be addressed
> during debugging
In the past, many softwares have used an error handler function to
provide the following cases:
1. Log the error in a more complicated way than PHP does by default.
2. Send off an email, if necessary, or communicate with another service.
3. Show a generic (e.g. a 500) error message to the client
On 10-Aug-06, at 6:02 AM, Michael Walter wrote:
Hi,
right now, PHP triggers fatal errors e.g. when accessing private
members or calling nonexistant functions. Since this is problematic
for obvious reasons, what technical reasons are there for that
behavior, and is there a chance that this beha
On 10-Aug-06, at 9:35 AM, Michael Walter wrote:
What do you feel is incorrect about allowing mentioned errors to be
handled in userspace?
My feeling is that errors such as visibility violations should be
addressed during debugging and Q&A phase where simple error logging
will be sufficien
What do you feel is incorrect about allowing mentioned errors to be
handled in userspace?
Regards,
Michael
On 8/10/06, Ilia Alshanetsky <[EMAIL PROTECTED]> wrote:
On 10-Aug-06, at 6:02 AM, Michael Walter wrote:
> Hi,
>
> right now, PHP triggers fatal errors e.g. when accessing private
> membe
Hi,
right now, PHP triggers fatal errors e.g. when accessing private
members or calling nonexistant functions. Since this is problematic
for obvious reasons, what technical reasons are there for that
behavior, and is there a chance that this behaviour will change in a
future release?
Regards,
Mi
