This sounds like a serious issue, but I'm not sure if it's in libxml
or in ext/soap. Will have a look later; but maybe Dmitry or someone
else knows off the top of their heads?
- David
Begin forwarded message:
From: Davide Romanini
Date: 30. Juni 2009 11:49:30 MESZ
To: s...@lists.php.net
Hi David,
Please report a bug on bugs.php.net (assign it to dmitry).
I'll look into it later.
Thanks. Dmitry.
David Zülke wrote:
> This sounds like a serious issue, but I'm not sure if it's in libxml or
> in ext/soap. Will have a look later; but maybe Dmitry or someone else
> knows off the top o
Can do, but I wanted to figure out a way to create a reproduce case
first (I already have an idea).
- David
On 24.07.2009, at 12:20, Dmitry Stogov wrote:
Hi David,
Please report a bug on bugs.php.net (assign it to dmitry).
I'll look into it later.
Thanks. Dmitry.
David Zülke wrote:
This
David Zülke ha scritto:
> Can do, but I wanted to figure out a way to create a reproduce case
> first (I already have an idea).
>
> - David
>
>
>
> On 24.07.2009, at 12:20, Dmitry Stogov wrote:
>
>> Hi David,
>>
>> Please report a bug on bugs.php.net (assign it to dmitry).
>> I'll look into it
On 24.07.2009, at 12:45, Davide Romanini wrote:
David Zülke ha scritto:
Can do, but I wanted to figure out a way to create a reproduce case
first (I already have an idea).
- David
On 24.07.2009, at 12:20, Dmitry Stogov wrote:
Hi David,
Please report a bug on bugs.php.net (assign it to dm
I published a (work in progress) RFC today about replacing certain
errors with exceptions. I know that there already was something similiar
on the php6dev blog, but this is not completly the same, so awating your
comments:
http://wiki.php.net/rfc/errors_as_exceptions
--
PHP Internals - PHP Runti
On Fri, Jul 24, 2009 at 3:23 PM, wrote:
> I published a (work in progress) RFC today about replacing certain
> errors with exceptions. I know that there already was something similiar
> on the php6dev blog, but this is not completly the same, so awating your
> comments:
>
> http://wiki.php.net/rfc
2009/7/24 :
> I published a (work in progress) RFC today about replacing certain
> errors with exceptions. I know that there already was something similiar
> on the php6dev blog, but this is not completly the same, so awating your
> comments:
>
> http://wiki.php.net/rfc/errors_as_exceptions
>
I'm
To you both, this is especially, for library code like Zend Framework.
The library cannot expect the user to have the error handle set, so it
would have to replace the error handler before every line which it wants
to try {} and reset it after the catch. This is not really a clean
solution, at it c
Please don't top post
2009/7/24 Ben Scholzen 'DASPRiD' :
> To you both, this is especially, for library code like Zend Framework.
> The library cannot expect the user to have the error handle set, so it
> would have to replace the error handler before every line which it wants
> to try {} and rese
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kalle Sommer Nielsen wrote:
> Then ZF should provide an error handler that can be called inside the
> user's error handler or simply choose to not use error handlers if the
> user have a custom error handler. I can't really see why the whole
> language
On 24.07.2009, at 16:06, Ben Scholzen 'DASPRiD' wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kalle Sommer Nielsen wrote:
Then ZF should provide an error handler that can be called inside the
user's error handler or simply choose to not use error handlers if
the
user have a custom e
On Fri, Jul 24, 2009 at 15:43, Ben Scholzen 'DASPRiD' wrote:
> To you both, this is especially, for library code like Zend Framework.
> The library cannot expect the user to have the error handle set, so it
> would have to replace the error handler before every line which it wants
> to try {} and r
On Fri, Jul 24, 2009 at 6:29 PM, Hannes
Magnusson wrote:
> On Fri, Jul 24, 2009 at 15:43, Ben Scholzen 'DASPRiD' wrote:
>> To you both, this is especially, for library code like Zend Framework.
>> The library cannot expect the user to have the error handle set, so it
>> would have to replace the er
On Fri, Jul 24, 2009 at 16:35, Alexey Zakhlestin wrote:
> On Fri, Jul 24, 2009 at 6:29 PM, Hannes
> Magnusson wrote:
>> On Fri, Jul 24, 2009 at 15:43, Ben Scholzen 'DASPRiD'
>> wrote:
>>> To you both, this is especially, for library code like Zend Framework.
>>> The library cannot expect the user
On 7/24/09 6:43 AM, Ben Scholzen 'DASPRiD' wrote:
To you both, this is especially, for library code like Zend Framework.
This tends to invalidate your entire argument IMO. Changing the core
language because something is hard in an external framework that only a
small percentage of actual PHP
I agree, however there are certain aspects of PHP's errors that leave
a lot to be desired. For instance, a failed fopen or a failed socket
will often result in an uncatchable warning from php. Sure, you can
add a @ to the line but that's slow and doesn't tell you anything
about what happene
Sorry for top post, on my android. I disagree that php has perl phobia, but
I agree that a alternative to errors needs to be made. Your example is nice
but might have some tricky implementation details if php continued to throw
errors when it didn't detect $!. I.E. fopen(...) or throw new
CustomExc
Matt Wilson wrote:
> I agree, however there are certain aspects of PHP's errors that leave a
> lot to be desired. For instance, a failed fopen or a failed socket will
> often result in an uncatchable warning from php. Sure, you can add a @
> to the line but that's slow and doesn't tell you anything
Hello,
u...@domain.invalid wrote:
> I published a (work in progress) RFC today about replacing certain
> errors with exceptions. I know that there already was something similiar
> on the php6dev blog, but this is not completly the same, so awating your
> comments:
>
> http://wiki.php.net/rfc/erro
This sounds very similar to preconditions in Design by Contract. However,
preconditions validate input to the method as a whole, while the proposed
syntax only checks individual arguments one at a time. Thus the proposed
syntax has rather significan limitations compared to real preconditions.
For
On Jul 23, 2009, at 9:21 PM, Gwynne Raskind wrote:
Today, I just release a new version of the Log package, and I
attempted to tag this release in the same way. Unfortunately, I ran
into this error:
$ svn copy \
http://svn.php.net/repository/pear/packages/Log/trunk \
http://svn.php.net/repos
On Fri, 2009-07-24 at 15:00 -0400, Gwynne Raskind wrote:
> And I'm happy to announce that this is now fixed; creation of tags is
> now allowed. This comes alongside a bit of an overhaul of the entire
> set of hook scripts. See http://news.php.net/php.cvs/59765 if you're
> desperately curious
Johannes Schlüter wrote:
> On Fri, 2009-07-24 at 15:00 -0400, Gwynne Raskind wrote:
>> And I'm happy to announce that this is now fixed; creation of tags is
>> now allowed. This comes alongside a bit of an overhaul of the entire
>> set of hook scripts. See http://news.php.net/php.cvs/59765 if y
Hi,
On Fri, 2009-07-24 at 16:14 -0500, Greg Beaver wrote:
> I think it would be better to make the release process like this, with
> 5.3.1RC1 as an example:
>
> (1) svn copy http://svn.php.net/repository/php/php-src/branches/PHP_5_3
> http://svn.php.net/repository/php/php-src/branches/php_5_3_1RC
Hi,
README.UNICODE still talks about the unicode semantics switch, it
probably needs updating.
Greg
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
26 matches
Mail list logo
