On 4/11/08, Michael B Allen <[EMAIL PROTECTED]> wrote:
> On 4/11/08, Antony Dovgal <[EMAIL PROTECTED]> wrote:
> > On 10.04.2008 21:19, Michael B Allen wrote:
> >
> > > Can anyone recommend a method for debugging this issue?
> > >
> >
> > I'd start with --enable-debug and valgrind.
> >
> >
Why on earth would you have int, string, resource, etc "return type hints"
and then turn around and suggest for parameter hinting just add a scalar
type? That makes no sense and is so inconsistent.
static int function retarded(scalar $value) {
return (int) $value; // lol
}
Hi,
If a stream wrapper does not log errors, by default, we grab
strerror(errno) to figure out the error message, but this is not a good
idea for any wrapper but plain_wrapper for the obvious reason that errno
is not used by wrappers that don't use sys calls.
Is this patch against 5.3 acceptable
On 07.04.2008, at 19:59, Stanislav Malyshev wrote:
Hi!
Right if at all I would agree on having a type hint "scalar", but
not a separate one per type.
IMO (as already was discussed like 10 times?) "scalar" makes no
sense. It doesn't save you any checks, and doesn't provide any
useful inf
On 08.04.2008, at 12:13, Krister Karlström wrote:
Yes indeed you can implement it using the __call method, but it
would be more readable if the language structure itself would
support it. I suggested this just because I think that this is the
most common way of using overloading, thus this
