On Thursday 21 November 2002 08:04, Derick Rethans wrote:
I still think that an included file just should fail hard and I just
dont like this kind of obfucsication.
I agree with this 100%. It is IMHO a complete waste of time trying to handle
parse errors gracefully. Most solutions proposed in
John Coggeshall wrote:
If I hacked on the source a bit and got this redirect-error thing
working, would it Be perhaps worthy of a commit?
+1
Bye,
Ivan
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
Edin Kadribasic wrote:
On Thursday 21 November 2002 08:04, Derick Rethans wrote:
I still think that an included file just should fail hard and I just
dont like this kind of obfucsication.
I agree with this 100%. It is IMHO a complete waste of time trying to
handle parse errors gracefully.
*lol* !
You could do something like --enable-have-a-lzw-license
But noone can control this so unisys would consider anybody
using php with gif a criminal. And i do not want to know what
they think about the development of php. MAybe they find a
solution to stop us because
guys, how about we just like leave this for a couple of months till 2003
when the patent runs out?
-- james
-Original Message-
From: Marcus Borger [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 21, 2002 10:23 AM
To: Stefan Esser
Cc: [EMAIL PROTECTED]
Subject: Re: [PHP-DEV]
Derick Rethans [EMAIL PROTECTED] wrote... :
On Thu, 21 Nov 2002, John Coggeshall wrote:
Again, what about IIS, etc?
Who cares? :) It really would be much better if some person who thinks
IIS rulez fixes the ISAPI module. If that doesn't work correctly nobody
should use it at all.
Okay...
Well, even though I've yet to convince Derick and a few others... I did
see enough interest in this to create a patch. This creates two new
directives: error_redirect (bool) which turns this on/off, and
error_redirect_url (string) which is the URL to redirect to upon error.
In order for
Hello PHP-Developers
I have an idea!
I recently went through the pain of creating an ISAPI DLL for IIS and what
I found was that IIS was *incredibly* sensitive to things going wrong in
the DLL with the result that the IIS process would hang and the whole damn
machine would need a reboot on a
On Thu, Nov 21, 2002 at 10:25:57AM -, James Cox wrote:
guys, how about we just like leave this for a couple of months till 2003
when the patent runs out?
-- james
I was just joking... Anyway I dislike all this patent shit.
Stefan Esser
--
PHP Development Mailing List
Writing for newbies, I often heard them mentioning one things they liked about
PHP (before even trying to use it) - PHP errors are not 500 weird pages
made by your browser.
Moving fatal errors to HTTP 500 can be somewhat confusing, unless we
have a solid way handling ALL errors in some very
Shane (and everyone else):
Why don't we move PHP into a separate executable. Design a
thin ISAPI DLL which purely passes the data which the ISAPI
DLL exposes between the IIS process and the PHP process (or
process-pool for added reliability). The resulting page is
processed in the
Moving fatal errors to HTTP 500 can be somewhat confusing,
unless we have a solid way handling ALL errors in some very
logical way. In other words - powerful but clear enough to
understand and use for neo programmers.
Check out my patch and tell me what you think. Since this can be turned
First of all i like the way you did it.
But why do you cut the errors by using snprintf with maximum length
set to ERRORURL_BUF_LEN. Instead you can simply use spprintf
and we would get the whole message. I guess you did it because you
created a GET solution?
marcus
At 12:56 21.11.2002, John
First of all i like the way you did it.
But why do you cut the errors by using snprintf with maximum
length set to ERRORURL_BUF_LEN. Instead you can simply use
spprintf and we would get the whole message. I guess you did
it because you created a GET solution?
Well, I guess it could be
At 13:27 21.11.2002, John Coggeshall wrote:
First of all i like the way you did it.
But why do you cut the errors by using snprintf with maximum
length set to ERRORURL_BUF_LEN. Instead you can simply use
spprintf and we would get the whole message. I guess you did
it because you created a GET
In Real Life [Patent Pending], if you cripple your production site
in the middle of the night then go to bed, you won't have to worry
about any of this because you'd be unemployed in the morning.
I agree with Derick's assessment.
I always have the option of turning display errors off (which is
Mike Robinson wrote:
In Real Life [Patent Pending], if you cripple your production site
in the middle of the night then go to bed, you won't have to worry
about any of this because you'd be unemployed in the morning.
I assume then that you run regression tests for your web sites
after
On Thu, 21 Nov 2002, Ivan Ristic wrote:
Mike Robinson wrote:
In Real Life [Patent Pending], if you cripple your production site
in the middle of the night then go to bed, you won't have to worry
about any of this because you'd be unemployed in the morning.
I assume then that you
Guys,
I have been following the thread about error reporting thing and, I
think, it is all going off route.
Of course, the ideas John and Marcus working on both are very nice, they seem
to make many interested. But PHP's error reporting itself is very
limited. So, as often mentioned in past,
We were talking about parse errors here. php -l before you put it life
should be enough for that. And yes, I run that before 'cvs commit'.
Well, I am afraid that it is not that simple, as there are other
fatal errors that cannot be caught and where lint is useless. For
example,
I quite like Maxim's ideas myself.
+1
--- Maxim Maletsky [EMAIL PROTECTED] wrote:
I will start laying out some my thoughts to hopefully get a
discussion towards working on the complete error reporting logic.
I had an extensive experience implementing custom errors, so
approve or disapprove
hi everyone
i already checked the archives on this one, to no avail. apparantly php
doesn't treat cyrillic characters quite correctly, or i don't get it; and
this is an example: let's say i have a cyrillic string which i want to post
to another script which then again inserts it (into oracle). i
I will start laying out some my thoughts to hopefully get a discussion
towards working on the complete error reporting logic. I had an
extensive experience implementing custom errors, so approve or
disapprove my ideas.
I like your ideas too, but some of your suggestions need to
be
Ivan Ristic [EMAIL PROTECTED] wrote... :
I will start laying out some my thoughts to hopefully get a discussion
towards working on the complete error reporting logic. I had an
extensive experience implementing custom errors, so approve or
disapprove my ideas.
I like your
Does anyone have an idea on how to track down segfaults from a
production Apache 1.3.27/PHP 4.2.3 server? If I could just figure out
the URL for the page that died, it would go a very long way...
My Apache error_log file is filled with this stuff and it is hurting the
server's performance:
[Thu
Hi !
Did you have some stranges URL request in access_log ?
Michael-
- Original Message -
From: Steven Roussey [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, November 21, 2002 5:39 PM
Subject: [PHP-DEV] URL for segfaults
Does anyone have an idea on how to track down
hi everyone
i already checked the archives on this one, to no avail. apparantly php
doesn't treat cyrillic characters quite correctly, or i don't get it; and
this is an example: let's say i have a cyrillic string which i want to post
to another script which then again inserts it (into oracle). i
Throwing this idea on another time can sound rush. Rright now, when
our heads are occupied analysing error reporting, this can result
being more productive, IMO. And, it is till related anyway.
I don't mind, I just don't want the patch forgotten :)
Ivan
--
PHP Development Mailing List
Like Vergoz mentioned, just review the times in both files and you can
narrow down which page caused the seg fault.
On Thu, 2002-11-21 at 09:39, Steven Roussey wrote:
Does anyone have an idea on how to track down segfaults from a
production Apache 1.3.27/PHP 4.2.3 server? If I could just
No. And I wish access_log logged requests at the beginning of a request
and had the child pid. There has to be some way of discovering or
logging URLs and seeing if they complete without a segfault, at which
point I'd look for those that did not complete. Surely I'm missing
something simple...
I think RC1 is going quite well (with the exception of bcmath issues, I
believe?), so I propose putting out RC2 next week. If that one does just
swimmingly, we should be ready for the release.
-Andrei http://www.gravitonic.com/
For every complex problem,
John Coggeshall wrote:
Shane (and everyone else):
Why don't we move PHP into a separate executable. Design a
thin ISAPI DLL which purely passes the data which the ISAPI
DLL exposes between the IIS process and the PHP process (or
process-pool for added reliability). The resulting page is
Well, that's cool then! Why not simply include all this stuff with PHP
rather than supporting the flawed ISAPI that it currently is packaged
with?
On Thu, 21 Nov 2002, Shane Caraveo wrote:
John Coggeshall wrote:
Shane (and everyone else):
Why don't we move PHP into a separate
Steven Roussey wrote:
No. And I wish access_log logged requests at the beginning of a
request and had the child pid.
It would be very easy to write a custom module to log
that at the beginning of the request. Would that help?
Ivan
--
PHP Development Mailing List http://www.php.net/
To
Nick Loman wrote:
Well, that's cool then! Why not simply include all this stuff with PHP
rather than supporting the flawed ISAPI that it currently is packaged
with?
4.3 the windows cgi binary is compiled with fastcgi support. I'm going
to be testing the fastcgi on osx this week once I get
Yes. Ideally such that you can grep for the failed URLs. I can see this
as being very helpful to a lot of people. Debug modes don't work for
production servers and it is only there that it is showing itself.
BTW - Easy for you maybe!
Sincerely,
Steven Roussey
http://Network54.com/
Guys,
I've added an OCI8 function in CVS the other week. I've avoided its
release in RC1 so I can test it well, but it seems to be pretty stable
and can be released with RC2.
Since I never had to do this yet, I wanted to know a few things before I
mess up something:
1. How do I get it onto
On Thu, 21 Nov 2002, Maxim Maletsky wrote:
I've added an OCI8 function in CVS the other week. I've avoided its
release in RC1 so I can test it well, but it seems to be pretty stable
and can be released with RC2.
We dont put new functions in a release after we branched to make sure we
don't
Thanks, Derick,
Derick Rethans [EMAIL PROTECTED] wrote... :
On Thu, 21 Nov 2002, Maxim Maletsky wrote:
I've added an OCI8 function in CVS the other week. I've avoided its
release in RC1 so I can test it well, but it seems to be pretty stable
and can be released with RC2.
We dont
Well, I think I found the cause if not the cure. I posted a bug report
yesterday about zLib (http://bugs.php.net/?id=20535) that seems to be
the culprit for another crash. Since our output compression uses it as
well, I tried turning output compression off. No more segfaults.
Unfortunately, I'll
Steven Roussey wrote:
Yes. Ideally such that you can grep for the failed URLs. I can see this
as being very helpful to a lot of people. Debug modes don't work for
production servers and it is only there that it is showing itself.
BTW - Easy for you maybe!
Don't take my word, have a look
At 07:06 PM 11/21/2002 +0100, Sander Roobol wrote:
Hey,
Attached is a patch that makes the bcmath extension thread safe.
Very cool! Thanks a lot.
I'm new to all that TSRM stuff, but I think this should do it. I
replaced the old globals with TSRM globals (inspired by the CG() and the
I was looking at compile warnings for 4.3, and came across this
in Zend/zend.h
/* output support */
#define ZEND_WRITE(str, str_len)zend_write((str), (str_len))
#define ZEND_PUTS(str) zend_write((str), strlen((str)))
#define ZEND_PUTC(c)zend_write((c),
Yes, so that it'll be compatible with the way libc's putc() works (the
value is the written char).
Andi
At 01:20 PM 11/21/2002 -0800, Brad Bulger wrote:
I was looking at compile warnings for 4.3, and came across this
in Zend/zend.h
/* output support */
#define ZEND_WRITE(str, str_len)
Tried a bit with your implementation and i wonder why you
allow redeclared functions to be abstract:
class pass {
function show() {
echo Call to function show()\n;
}
}
class fail extends pass {
abstract function show();
}
Another thing i wonder is that
did you forget to return http 500 in the sapis?
-- james
-Original Message-
From: John Coggeshall [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 21, 2002 11:56 AM
To: 'PHP Developers Mailing List'
Subject: [PHP-DEV] [PATCH] Redirect on Error
Okay...
Well, even though
The point is that it should be possible to throw a HTTP 500 error. This is
really only useful in production environments, ie, when the code going live
should already be free of things like parse errors. Throwing a 500 error
would make it easier to merge into your already existing error handling
In Real Life [Patent Pending], if you cripple your production site
in the middle of the night then go to bed, you won't have to worry
about any of this because you'd be unemployed in the morning.
+1... don't commit code without QA!
I agree with Derick's assessment.
I always have the
Also, from a management point of view (I manage programmers),
what you are describing there can work in some cases but what
if a programmer forgets/is-too-lazy to to that? I don't want
to wait for the next morning to know about it.
if a programmer is too lazy to test, fire them.
What is so hard to understand in word 'FATAL'?
If your script doesn't work, what use is it to make it
show the cryptic 500 error??
I'm -10 for adding anything like this, even if and
even more then if it's optional.
Just forget this.
--Jani
On Thu, 21
In zend_API.c we do not initialize is_static for the registered function.
Therefore sometime they are static and sometimes not. We must
make those non static or provide the information in the call. Non static
is required for things like ext/domxml.
marcus
cvs -z3 -q diff zend_API.c (in directory
James Cox wrote:
Also, from a management point of view (I manage programmers),
what you are describing there can work in some cases but what
if a programmer forgets/is-too-lazy to to that? I don't want
to wait for the next morning to know about it.
if a programmer is too lazy to test,
It seems like the NULL type is a scalar type, ie it has a discrete set of
values. I suppose from an SQL perspective, one could argue NULL is a
special value that destroys any attempts at evaluation. However, PHP has a
precedent that relates to this issue: the ctype functions. For example,
Attached is a patch that fixes bug #19207 in accordance with previous
discussion on php-dev. It add cgi.rfc2616_headers ini option which is by
default set to off and mimics current 4.3.0 behaviour. If its set to on the
HTTP status line is sent in accordance to RFC2616 which was default for PHP
In the following link you will find final, public, protected and private (f
+ 3p) for ZE2:
http://marcus-boerger.de/php/ext/ze2/
What it does:
- introduced final, public, protected, private member functions (methods)
- Since we have aggregation already (and a patch from me some days
before
On Fri, 22 Nov 2002, Edin Kadribasic wrote:
Attached is a patch that fixes bug #19207 in accordance with previous
discussion on php-dev. It add cgi.rfc2616_headers ini option which is by
default set to off and mimics current 4.3.0 behaviour. If its set to on the
HTTP status line is sent in
Hi!
From head i get an error when I compile it.
config.nice:
'./configure' \
'--disable-all' \
'--prefix=/usr/local/www/php4cli' \
'--enable-debug' \
'--enable-sysvshm' \
'--enable-aggregate' \
'--enable-xslt' \
'--enable-bcmath' \
'--enable-calendar' \
'--enable-dbase' \
'--enable-dio' \
57 matches
Mail list logo
