Sebastian Bergmann wrote:
I updated to gcc 3.2 a while ago and it worked fine. This morning, for
instance, I was able to build HEAD without problems. Just now I was
able to build httpd-2.0 HEAD without problems.
I updated binutils and did a fresh checkout of /php4. Now it works
again.
--
Zeev Suraski wrote:
You print something, it doesn't print out. How is it trivial to solve
this? If you happen to know that there's IO buffering and that there's
a function called flush() then maybe it trivial, but then there are the
other million users who don't. Hence the idea of setting
Mike Ford wrote:
BTW, real language (i.e. not shell) don't flush. Please let me
know if there is real language that do automatic flushing by
default.
But PHP-CLI *is* a shell-scripting language, and therefore should behave
like one. Other flavours of PHP aren't, and shouldn't. QED.
You
Mike,
It seems my last mail is a bit too negative. Sorry.
Mike Ford wrote:
-Original Message-
From: Yasuo Ohgaki [mailto:yohgaki;ohgaki.net]
Sent: 24 October 2002 07:42
To: [EMAIL PROTECTED]; Alan Knowles
Alan Knowles wrote:
Im +1 for reverting the patch - (for what it's worth)
Yasuo,
can you please stop this discussion now, it's not going to change. It
only wastes time which we could have spend on numerous other things for
PHP, such as fixing bugs and writing tests for the test system.
Derick
On Fri, 25 Oct 2002, Yasuo Ohgaki wrote:
Mike,
It seems my last
Hello,
to make easier maintenance and checking possible I would suggest to name
our tests more appropriate:
Class: Name: Example:
Tests for bugs bugbugid.phptbug17123.phpt
Tests for functions functionname.phpt
+1
Moriyoshi
Derick Rethans [EMAIL PROTECTED] wrote:
Hello,
to make easier maintenance and checking possible I would suggest to name
our tests more appropriate:
Class: Name: Example:
Tests for bugs bugbugid.phptbug17123.phpt
In my PHP-Version, Session-IDs are appended like this:
script.php?foo=4PHPSESSID=344e...
To be XHTML1-compliant it should be done this way:
script.php?foo=4amp;PHPSESSID=344e...
Is there any way I could PHP force to do this except adding
the Session-IDs manually or change the PHP-Code? Sorry,
On Fri, 25 Oct 2002, Jens Lehmann wrote:
In my PHP-Version, Session-IDs are appended like this:
script.php?foo=4PHPSESSID=344e...
To be XHTML1-compliant it should be done this way:
script.php?foo=4amp;PHPSESSID=344e...
Is there any way I could PHP force to do this except adding
the
On Fri, 25 Oct 2002, Jens Lehmann wrote:
In my PHP-Version, Session-IDs are appended like this:
script.php?foo=4PHPSESSID=344e...
To be XHTML1-compliant it should be done this way:
script.php?foo=4amp;PHPSESSID=344e...
Is there any way I could PHP force to do this except adding
At 11:57 25-10-2002, Derick Rethans wrote:
to make easier maintenance and checking possible I would suggest to name
our tests more appropriate:
+1
Class: Name: Example:
Tests for bugs bugbugid.phptbug17123.phpt
Tests for functions
On Fri, Oct 25, 2002 at 11:57:34AM +0200, Derick Rethans wrote:
to make easier maintenance and checking possible I would suggest to name
our tests more appropriate:
Class: Name: Example:
Tests for bugs bugbugid.phptbug17123.phpt
On Fri, 25 Oct 2002, Melvyn Sopacua wrote:
At 11:57 25-10-2002, Derick Rethans wrote:
[snip]
I do not see a real use to rename tests, but IMO this is the way to go
for newly written tests. Of course renaming tests is ok too if you like
to do that :)
There's one drawback. Extensions with
At 09:15 25/10/2002, Yasuo Ohgaki wrote:
Zeev Suraski wrote:
You print something, it doesn't print out. How is it trivial to solve
this? If you happen to know that there's IO buffering and that there's a
function called flush() then maybe it trivial, but then there are the
other million
At 12:49 25-10-2002, Derick Rethans wrote:
[...]
There's one drawback. Extensions with names after 'b' get evaluated after
the bug tests.
This is currently not a problem, but I've been playing with the thought to
introduce 'skip_ext' to speed things up:
--SKIP--
?php
Hi,
i've a small problem with the signal handler.
These short script demonstrate my problem.
#!/usr/local/bin/php
?php
set_time_limit(0);
function signals($signo) {
switch($signo) {
case SIGTERM:
echo Termination signal;
Hi People,
I am running PHP 4.1.2 on a Cobalt Raq4 server. I'm pretty new to Linux and
can't understand why the server has come preinstalled with 2 diffrent
versions of PHP. When I run phpinfo() from scripts on the site through my
browser it says PHP is installed as an Apache module, but when I
On Fri, Oct 25, 2002 at 01:39:15PM +0100, Chris Morrow wrote :
Hi People,
I am running PHP 4.1.2 on a Cobalt Raq4 server. I'm pretty new to Linux and
can't understand why the server has come preinstalled with 2 diffrent
versions of PHP. When I run phpinfo() from scripts on the site through
There were some changes to the pcntl extension. Have a look at
http://www.zend.com/lists/php-dev/200208/msg00937.html
Edin
- Original Message -
From: Steve Alberty [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, October 25, 2002 2:35 PM
Subject: [PHP-DEV] pcntl_signal problem
On Fri, 2002-10-25 at 08:50, Edin Kadribasic wrote:
There were some changes to the pcntl extension. Have a look at
http://www.zend.com/lists/php-dev/200208/msg00937.html
Edin
- Original Message -
From: Steve Alberty [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, October
On Fri, Oct 25, 2002 at 11:50:46AM -0500, Jason Greene wrote :
I will be updating the documentation to explain this before 4.3 is
released, but I wonder If I should have configure spit out a reminder
whenever someone enables pcntl
-1
No reminder, no E_WARNING. People should read
I'm trying to add my new function, register_offline_function, and have it
pretty much finished, but need a few pointers.
The php_request_function in main/main.c is where I'm working currently.
I've set up the function very similarly to the current
register_shutdown_function mechanism, and I've
Hi,
My email was dead in the past 24 hours. All email I received was lost. If
there's anything important you wanted me to read please email it to me again.
Thanks,
Andi
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
I haven't installed xslt yet so i do not know...but i am testing with 25% of
the modules and get the feeling that we must check for all warnings and
errors.
A special situation is ext/session/tests/008-php4.2.3.phpt
where a warning mechanism is checked..here the following would be enough
On October 25, 2002 04:01 pm, Marcus Börger wrote:
I haven't installed xslt yet so i do not know...but i am testing with 25%
of the modules and get the feeling that we must check for all warnings and
errors.
A special situation is ext/session/tests/008-php4.2.3.phpt
where a warning mechanism
But we are speaking about one single test. I mean multiple calls to
$php_errormsg
are allowed of cause. I was just looking for a solution to check whether a
test
produces any not wanted messages.
marcus
At 22:06 25.10.2002, Ilia A. wrote:
On October 25, 2002 04:01 pm, Marcus Börger wrote:
I
At 22:36 25-10-2002, Ilia A. wrote:
I've just tried the latest version of the xslt tests and
ext/xslt/tests/xslt_setopt.phpt test fails. The failure is the result of
expected output needing some non-ascii character after PHP QA. Where is this
character comming from, the xml xslt style sheets do
Zeev Suraski wrote:
At 09:15 25/10/2002, Yasuo Ohgaki wrote:
Zeev Suraski wrote:
You print something, it doesn't print out. How is it trivial to
solve this? If you happen to know that there's IO buffering and that
there's a function called flush() then maybe it trivial, but then
there
Derick Rethans wrote:
Yasuo,
can you please stop this discussion now, it's not going to change. It
only wastes time which we could have spend on numerous other things for
PHP, such as fixing bugs and writing tests for the test system.
I don't want to waste my time too. I just trying to make
I need to add a little.
Zeev Suraski wrote:
If we are argue about difficulty of flushing,
We're not. We're arguing about the obscurity of the problem.
Are you going to set output_buffering=Off by default, too?
Since the obscurity still exists with output buffers.
It's even worse with
At 01:22 26-10-2002, Yasuo Ohgaki wrote:
Makefile.global
- You insisted it should be INI independent without fixing
dependency issue
Some settings cannot be hardcoded. Granted.
Some we may want to hardcode for run-tests.php. Granted.
php.ini-dist is not the one to do it with. It's
Hello,
I've just joined the list to send this patch hoping
this helps
with the development of PHP...
I wanted to build PHP 4.2.3 against gd 2.0.4
(latest
version) and it would compile.
I found the problem is one member of
the
gdIOCtx struct in gd_io.h has been renamed
from
"free" to
Melvyn Sopacua wrote:
*SNIP*
If there should be something to fix, via an ini file, than let's
use php.ini-test.
No objection from me, of course.
It's even better since we don't care about changes in php.ini-dist.
--
Yasuo Ohgaki
--
PHP Development Mailing List http://www.php.net/
To
I'd like to work on the documentation, cleaning up some of the comments and updating a
few of the pages. So I guess that means phpdoc access :-) I might also get involved
with the translations.
Who sent me? Well... I just got back from PHPCon where I met Rasmus, yay! Jim Winstead
suggested
34 matches
Mail list logo
