Sara Golemon wrote:
bool is_readable ( string filename [, bool use_include_path] )
we can always dream ..
I prefer the word "mature" instead of dream ;)
How about something which will save having to resolve that path twice?
$realpath = stream_resolve_include_path($relativepath);
if ($re
bool is_readable ( string filename [, bool use_include_path] )
we can always dream ..
so far the answer has been that this parameter should never have been
added to fopen(), and that file_exists(), is_readable and friends should
never get this feature. IIRC the reason was that they should not
On 10/8/06, Pierre <[EMAIL PROTECTED]> wrote:
Hello,
On 10/8/06, Hannes Magnusson <[EMAIL PROTECTED]> wrote:
> On 10/8/06, Pierre <[EMAIL PROTECTED]> wrote:
> > Hello,
> >
> > On 10/8/06, Hannes Magnusson <[EMAIL PROTECTED]> wrote:
> > > imagefilter() currently throws double "wrong param count"
Hello,
On 10/8/06, Hannes Magnusson <[EMAIL PROTECTED]> wrote:
On 10/8/06, Pierre <[EMAIL PROTECTED]> wrote:
> Hello,
>
> On 10/8/06, Hannes Magnusson <[EMAIL PROTECTED]> wrote:
> > imagefilter() currently throws double "wrong param count" error.
> > Attached is a patch for HEAD that fixes it.
>
On 10/8/06, Pierre <[EMAIL PROTECTED]> wrote:
Hello,
On 10/8/06, Hannes Magnusson <[EMAIL PROTECTED]> wrote:
> imagefilter() currently throws double "wrong param count" error.
> Attached is a patch for HEAD that fixes it.
You just asked me on IRC and I told you to post one patch to fix all
simi
Hello,
On 10/8/06, Hannes Magnusson <[EMAIL PROTECTED]> wrote:
imagefilter() currently throws double "wrong param count" error.
Attached is a patch for HEAD that fixes it.
You just asked me on IRC and I told you to post one patch to fix all
similar issues at once. Why are you posting this ques
imagefilter() currently throws double "wrong param count" error.
Attached is a patch for HEAD that fixes it.
-Hannes
Index: ext/gd/gd.c
===
RCS file: /repository/php-src/ext/gd/gd.c,v
retrieving revision 1.358
diff -u -r1.358 gd.c
---
On 9/25/06, Matt W <[EMAIL PROTECTED]> wrote:
Hi,
Don't know if someone wants to check this out and apply it before 5.2's
release, or whether you want it at all. ;-) I just noticed how many of the
php_error_docref()'s still have a period (".") at the end of the text,
resulting in "... error mes
