Andi,
Marcus didn't commit this patch.
BTW: I am glad with existing syntax and semantic and don't see any reason to
change them.
They are simular to other programming languages.
Thanks. Dmitry.
> -Original Message-
> From: Andi Gutmans [mailto:[EMAIL PROTECTED]
> Sent: Monday, Januar
Well, the program that I'm really doing this with has a -o option to
write its data out to a file and when I use that option I have the same
problem with it only taking the first 64KB on stdin.
On Mon, Jan 23, 2006 at 04:48:12AM GMT, Nicolas Bérard Nault [EMAIL PROTECTED]
said the following:
>
My guess at first look is that you fill the stdout buffer because you don't
read from it untill you stop piping data to stdin.
On 1/22/06, Mark Krenz <[EMAIL PROTECTED]> wrote:
>
>
> I asked this last night on the general mailing list and also have
> asked around about it. Nobody seems to know.
I asked this last night on the general mailing list and also have
asked around about it. Nobody seems to know. I normally wouldn't ask a
support quesiton on a developers mailing list, but nobody else seems to
know so I thought that perhaps a developer knows.
Why would I be running into this
Yes, this was by design. Via class it should be ::method() and via
object it should be ->method().
Why do you think this is wrong? I think it actually makes a lot of
sense and don't see what we gain from allowing to call
self->method(). If there's a good reason, I'd be open to it though.
And ple
On Sat, 21 Jan 2006, Derick Rethans wrote:
On Fri, 20 Jan 2006, Rasmus Lerdorf wrote:
I am all for the filter extension as well obviously, but I agree there is a
bit of cleanup needed and I have a bunch of things I'd like to see in it, but
none of them necessarily block adding it.
What would y
Hello internals,
right now we allow 'class::method()' like syntax but not 'class->method()
like. If noone comes up with a valid reason why i am forced to call
a parents method using static syntax i'll commit the little required
change. We could even add an E_STRICT when the old syntax is used wher
That could work. Since arrays in javascript are numeric only, one
could determine if a structure is an object or an array. However,
there are no functions to determine if an array contains associative
items, so that would have to be implemented in userland.
Being able to encode arrays to JSON
Daniel Convissor wrote:
Exactly what I was going to say.
The one thing I'd like to see change is having JSON "objects" decoded into
PHP associative arrays, not PHP objects, as is done in the current PECL
implementation. Here's what happens now via PECL JSON:
Maybe introduce an optional sec
