Hans-Peter Oeri wrote:
Hi!
As documented - and several searches did not lead to a different result
- XMLReader and XMLWriter can only work on an URI. That would be a php
stream opened and closed by themselves.
For several workflows, e.g. with php://temp, it would be nice to be able
to attach
On 17 Jun 2010, at 20:14, Stas Malyshev wrote:
Hi!
I know the discussion is about scalar type hints. But what is with a
object type hint as base for all objects?
When it makes sense to accept any object, regardless of the class, but not
other types? I wonder if it's really a common
On 18.06.2010, at 16:13, Melanie Rhianna Lewis wrote:
On 17 Jun 2010, at 20:14, Stas Malyshev wrote:
Hi!
I know the discussion is about scalar type hints. But what is with a
object type hint as base for all objects?
When it makes sense to accept any object, regardless of the
On Fri, 18 Jun 2010 16:28:31 +0200, Lukas Kahwe Smith m...@pooteeweet.org
wrote:
On 18.06.2010, at 16:13, Melanie Rhianna Lewis wrote:
On 17 Jun 2010, at 20:14, Stas Malyshev wrote:
Hi!
I know the discussion is about scalar type hints. But what is with a
object type hint as base for
On 18.06.2010, at 18:13, Christian Kaps wrote:
On Fri, 18 Jun 2010 16:28:31 +0200, Lukas Kahwe Smith m...@pooteeweet.org
wrote:
On 18.06.2010, at 16:13, Melanie Rhianna Lewis wrote:
On 17 Jun 2010, at 20:14, Stas Malyshev wrote:
Hi!
I know the discussion is about scalar type
On 18 June 2010 15:13, Melanie Rhianna Lewis cybersp...@php.net wrote:
On 17 Jun 2010, at 20:14, Stas Malyshev wrote:
Hi!
I know the discussion is about scalar type hints. But what is with a
object type hint as base for all objects?
When it makes sense to accept any object, regardless of
On Thu, 2010-06-17 at 18:43 -0400, Mike Robinson wrote:
On June-17-10 12:44 PM Pierre Joye wrote:
The only voice that matters here is the voice of the mysql team, they
know if it is still widely used or not, and how :)
The voice that matters is internals at large.
Really? Seriously, how
On Wed Jun 16 07:04 AM, Ilia Alshanetsky wrote:
drop the Sqlite2 extensions from Trunk as they are superseded by
the
Sqlite3
extensions. The sqlite2 library is no longer maintainer and the
migration path from version 2 to 3 is very simple. Unless there
any objections, I'd like to
On Jun 18, 2010, at 10:50 AM, Jonathan Bond-Caron wrote:
On Wed Jun 16 07:04 AM, Ilia Alshanetsky wrote:
drop the Sqlite2 extensions from Trunk as they are superseded by
the
Sqlite3
extensions. The sqlite2 library is no longer maintainer and the
migration path from version 2 to 3 is very
Johannes Schlüter schrieb:
As I said before in this thread: Realistically we can't drop it. Too
many tutorials, books, applications, ... mention mysql_* and ignore the
limitations and issues the old mysql extension provides...
True, true...
One of the best things one can do is to bash very
10 matches
Mail list logo