This was originally posted to php-general, but for some reason I believe
it may belong here. I apologize if I'm wrong.
Forgive me for my ignorance, but I've noticed some unwanted behavior
(IMO, at least) with the is_link() function. Given the simple code..
if ( is_link
ID: 10468
Updated by: torben
Reported By: [EMAIL PROTECTED]
Status: Closed
Bug Type: Unknown/Other Function
PHP Version: 4.0.4pl1
Assigned To:
Comments:
Your feeling is correct--while PHP 4 is downwardly compatible
with PHP 3 in most respects, there are differences. There is a
migration
ID: 10464
User Update by: [EMAIL PROTECTED]
Status: Open
Bug Type: Apache related
Description: PHP_AUTH_PW is not set altough PHP_AUTH_USER is
Update: register_globals is turned on.
(see
http://www-usercgi.tu-chemnitz.de/~tisc/authtest.php3
for output of phpinfo() after authentication.)
At 03:02 24/4/2001, Anil Madhavapeddy wrote:
It a bit of a showstopper for pretty much all web-based mail clients
like IMP - people have been reporting their logs being littered with
segfaults for a while now actually.
Ok then, merge it in, and looks like we'll have to have RC8 after all.
Zeev
Yeah, it's been reported - RC7 identifies itself as RC6. It's still RC7
though :)
At 06:33 24/4/2001, Jon Rosenberg wrote:
I went through my server and deleted all files and directories associated
with RC6, then went ahead and compiled RC7 with the same options, I deleted
everything first b/c
From: [EMAIL PROTECTED]
Operating system: Linux Slackware 7.1+
PHP version: 4.0.4pl1
PHP Bug Type: ODBC related
Bug description: ODBC_result() fails on DB2 LONG VARCHAR columns
Running on IBM DB2 UDB version 7.1 for Linux, PHP compiled with --with-ibm-db2
configure option.
On Tue, 24 Apr 2001, Zeev Suraski wrote:
At 03:02 24/4/2001, Anil Madhavapeddy wrote:
It a bit of a showstopper for pretty much all web-based mail clients
like IMP - people have been reporting their logs being littered with
segfaults for a while now actually.
Ok then, merge it in, and
From: [EMAIL PROTECTED]
Operating system: Linux (Mandrake 7.2)
PHP version: 4.0.4pl1
PHP Bug Type: HTTP related
Bug description: Authorization not read by getallheaders()
I cannot read the Authorization header via getallheaders function.
But if i use phpinfo() in the same
At 12:03 24/4/2001, Sascha Schumann wrote:
On Tue, 24 Apr 2001, Zeev Suraski wrote:
At 03:02 24/4/2001, Anil Madhavapeddy wrote:
It a bit of a showstopper for pretty much all web-based mail clients
like IMP - people have been reporting their logs being littered with
segfaults for a while
From: [EMAIL PROTECTED]
Operating system: Windows 98
PHP version: 4.0.4pl1
PHP Bug Type: MySQL related
Bug description: Warning: Access denied for user: 'john@BOB' (Using password: YES) in
./db_mysql
Have not had much luck with mysql (probably because i have only used
ID: 10471
Updated by: hholzgra
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Bogus
Bug Type: MySQL related
PHP Version: 4.0.4pl1
Assigned To:
Comments:
this is a bug database, not a support forum
please ask questions on the php-general mailing list
(to be found under support on
From: [EMAIL PROTECTED]
Operating system: Linux
PHP version: 4.0.3pl1
PHP Bug Type: *Session related
Bug description: with session, IE not parse html header
In php 4.0.3pl1, with session
IE doesn't parse html header.
only not using php, you can see IE page infomation.
On Tue, 24 Apr 2001, Zeev Suraski wrote:
At 12:03 24/4/2001, Sascha Schumann wrote:
On Tue, 24 Apr 2001, Zeev Suraski wrote:
At 03:02 24/4/2001, Anil Madhavapeddy wrote:
It a bit of a showstopper for pretty much all web-based mail clients
like IMP - people have been reporting their logs
From: [EMAIL PROTECTED]
Operating system: Solaris 2.6
PHP version: 4.0.4pl1
PHP Bug Type: Apache related
Bug description: DSO loading and core dumped
I've tried to load the PHP 4.0.4pl1 shared object module(named libphp4.so). and I've
captured the truss message.
If I
ID: 7782
User Update by: [EMAIL PROTECTED]
Status: Open
Bug Type: Feature/Change Request
Description: Cannot use PATH_INFO fully with php isapi
Hi,
Due to some problems we have had with the isapi version of php under IIS,
we have made some changes in the sourcecode of this isapi module to
Manesh:
This, the php-dev list, is for discussion of the development of the PHP
Language itself. Questions pertaining to development *USING* the PHP
language should be addressed to [EMAIL PROTECTED]
- Original Message -
From: Manesh [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent:
A reproducible crash bug in a mainstream module is a show stopper IMHO...
Zeev
At 14:16 24/4/2001, Jani Taskinen wrote:
On Tue, 24 Apr 2001, Zeev Suraski wrote:
At 12:03 24/4/2001, Sascha Schumann wrote:
On Tue, 24 Apr 2001, Zeev Suraski wrote:
At 03:02 24/4/2001, Anil Madhavapeddy
At 03:59 PM 4/24/2001 +0300, Zeev Suraski wrote:
A reproducible crash bug in a mainstream module is a show stopper IMHO...
I think you mean in a mainstream module and in a situation which has a high
chance of happening.
Crash bugs which are 1 in a million don't necessarily need to be show
Not necessarily; Crash bugs can very often lead to security issues. Of
course, it's a clearer cut if it's in a situation which is very likely to
happen.
Zeev
At 17:09 24/4/2001, Andi Gutmans wrote:
At 03:59 PM 4/24/2001 +0300, Zeev Suraski wrote:
A reproducible crash bug in a mainstream
On Tue, Apr 24, 2001 at 12:26:34PM +0300, Zeev Suraski wrote:
The race between world peace and PHP 4.0.5 is tightening by the minute :)
Anyway, let's say Wednesday evening (GMT) would be the last time to put in
changes; RC8 goes out then; 4.0.5 goes out on Monday, unless there are
Well you want me to merge the foreach() fix then? I don't because I prefer
it being tested for a while so that we don't have a pl1.
I don't think we fix all crash bugs every release. Mainly buffer overflows
are dangerous. Not double free()'s or de-referencing NULL pointers. But of
course, a
RC7 still appends a binary zero to every element in the array
returned by get_defined_functions(). IIRC Andrei said he fixed
it (but maybe in HEAD only?).
Seems like it'd be easy to fix, shouldn't it be done for 4.0.5?
At 22:23 23.4. 2001, Zeev Suraski wrote the following:
I see it in RC7.
On Tue, 24 Apr 2001, Andi Gutmans wrote:
Looks like it got merged before RC7.
Can you check if your source includes this fix?
From: Andrei Zmievski [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Mon, 02 Apr 2001 16:12:07 -
Subject: [PHP-CVS] cvs: php4(PHP_4_0_5)
On Tue, 24 Apr 2001, Cynic wrote:
RC7 still appends a binary zero to every element in the array
returned by get_defined_functions(). IIRC Andrei said he fixed
it (but maybe in HEAD only?).
Seems like it'd be easy to fix, shouldn't it be done for 4.0.5?
It's been merged into the release
Hello...
I'm banging around on PHP 4.0.5 RC7 Win32 (Apache module), and I'm having great
difficultly getting the TRANS_SID feature to work. I have one web application which
depends heavily on it, and it's unusable under 4.0.5RC7.
Has anyone else been experiencing this difficultly?
- Matt
Did this work in the past? If so, any idea when it stopped working?
Andi
At 10:13 AM 4/24/2001 -0400, Matt White wrote:
Hello...
I'm banging around on PHP 4.0.5 RC7 Win32 (Apache module), and I'm having
great difficultly getting the TRANS_SID feature to work. I have one web
application which
At 17:24 24/4/2001, Andi Gutmans wrote:
Well you want me to merge the foreach() fix then? I don't because I prefer
it being tested for a while so that we don't have a pl1.
The plan is to release 4.0.5 four days after RC8.
I don't think we fix all crash bugs every release. Mainly buffer
Hi!
Maybe, I'm not so correct, or something else, but. Try to run the
script (php 4.0.6-dev).
Compiled with:
./configure --with-sablot
--with-dom --with-gettext --with-jpeg-dir=/usr --with-pops
--with-xml=/usr/local --with-gdbm=/usr/local --enable-gd-native-ttf
--with-gd --with-freetype-dir
At 12:03 24/4/2001, Sascha Schumann wrote:
On Tue, 24 Apr 2001, Zeev Suraski wrote:
At 03:02 24/4/2001, Anil Madhavapeddy wrote:
It a bit of a showstopper for pretty much all web-based mail clients
like IMP - people have been reporting their logs being littered with
segfaults for
ID: 10466
Updated by: jmoore
Reported By: [EMAIL PROTECTED]
Old-Status: Closed
Status: Bogus
Bug Type: Filesystem function related
PHP Version: 4.0.4pl1
Assigned To:
Comments:
Previous Comments:
---
[2001-04-23 17:13:21]
ID: 10466
User Update by: [EMAIL PROTECTED]
Status: Bogus
Bug Type: Filesystem function related
Description: hidden '.' files don't work with file_exists()
single quotes solved it.
thanks...
Previous Comments:
---
From: [EMAIL PROTECTED]
Operating system: FreeBSD
PHP version: 4.0.2
PHP Bug Type: Documentation problem
Bug description: wrong object in an example, german doc
function.mysql-fetch-field.html
WRONG:
echo PRE
blob: $meta - blob
max_length: $meta - max_length
On Tue, Apr 24, 2001 at 08:00:47PM +0400, Vadka wrote:
?
$Bad=0; // try to set it to 1 for segfault
$taggz[0]=table_here;
$taggz[1]=mydir;
$functinz['table_here']=my_func;
$functinz['mydir']=my_func;
error_reporting(E_ALL);
Function my_func($atr){
echo(Variable:-);
On Tue, 24 Apr 2001, Jon Parise wrote:
[trimmed]
Would you say this is the same problem that I reported a while
back?
http://www.php.net/bugs.php?id=6175
Yes, it is, as I can see. The problem remains. For now, I have no so
much time to
hack it, but it seems that the pointer is assumed
More, calling xml_parse_into_struct after normal xml_parse cause the
segfault too (repeating of xml_parse will cause no error).
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list
From: [EMAIL PROTECTED]
Operating system: FreeBSD
PHP version: 4.0.4pl1
PHP Bug Type: *Function Specific
Bug description: Array returned by str_replace unusable.
See http://sbw.sbw.org/str_replace/.
str_replace(-string-, -string-, -array-) should return an array.
It
ID: 10475
Updated by: andrei
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Closed
Bug Type: *Function Specific
PHP Version: 4.0.4pl1
Assigned To:
Comments:
It works in latest CVS.
$input = array('foobar', 'barhop');
var_dump(implode(' : ', str_replace('bar', '---', $input)));
From: [EMAIL PROTECTED]
Operating system: RedHat 6.2
PHP version: 4.0.4pl1
PHP Bug Type: Documentation problem
Bug description: search ofonline documentation
The search engine are not working in www.php.net.
--
Edit Bug report at: http://bugs.php.net/?id=10476edit=1
ID: 10476
Updated by: derick
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Bogus
Bug Type: Documentation problem
PHP Version: 4.0.4pl1
Assigned To:
Comments:
Please report this to [EMAIL PROTECTED] This site is for reporting bugs in PHP.
Thx for this notification.
Derick
Previous
From: [EMAIL PROTECTED]
Operating system: linux 2.2
PHP version: 4.0.4pl1
PHP Bug Type: Output Control
Bug description: ob_start('function') is called before trans-sid is applied, not after
?php
if (isset($PATH_INFO))
{
$var = explode('/',
From: [EMAIL PROTECTED]
Operating system: Redhat 7.0
PHP version: 4.0.4pl1
PHP Bug Type: *Configuration Issues
Bug description: --with-mcrypt leads to configure: error: Sorry
My configure line used to work on a redhat 6.2 system.
Now I have upgraded, it does not work any
Parse error: parse error, expecting `T_PAAMAYIM_NEKUDOTAYIM' or `'('' in
/path/to/file.php on line 246
Zeev/Andi ... ? :)
- Colin
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the
On Tue, 24 Apr 2001, Colin Viebrock wrote:
Parse error: parse error, expecting `T_PAAMAYIM_NEKUDOTAYIM' or `'('' in
/path/to/file.php on line 246
Zeev/Andi ... ? :)
Read expecting '::' or '('.
-Andrei
Commitment, n.:
Commitment can be illustrated by a breakfast of ham and eggs. The
On Tue, Apr 24, 2001 at 08:00:47PM +0400, Vadka wrote:
Hi!
frag
to get this working you have to say:
class hallo {
//...
function hallo($bla) {
// ^ this is important!
$this-parser = xml_parser_create();
From: [EMAIL PROTECTED]
Operating system: Solaris
PHP version: 4.0 Latest CVS (24/04/2001)
PHP Bug Type: *Configuration Issues
Bug description: Failure to recognize libsybdb.so
Despite specification of --with-sybase=/sybase_dir ,
libphp4.so attempts to load
From: [EMAIL PROTECTED]
Operating system: Windows 2000
PHP version: 4.0.4pl1
PHP Bug Type: IIS related
Bug description: ISAPI module conflicts with asp.dll
I'm having the problem that has been reported before (looking at past bug reports)
about the isapi .dll conflicting
ID: 10480
User Update by: [EMAIL PROTECTED]
Status: Open
Bug Type: IIS related
Description: ISAPI module conflicts with asp.dll
Original comment:
I'm having the problem that has been reported before (looking at past bug reports)
about
the isapi .dll conflicting with asp.dll. When I run a php
On Tue, Apr 24, 2001 at 08:31:26PM +0200, Thies C. Arntzen wrote:
[workaround snipped]
the problem here a cyclic references _and_ $this _not_ being
the instantiated object (unless u use this ugly ampersand
hack as illustrated)
Granted, it is a problem that can be worked around
ID: 10478
Updated by: derick
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Feedback
Bug Type: *Configuration Issues
PHP Version: 4.0.4pl1
Assigned To:
Comments:
Can you send me your configure.log file (privately)?
Derick
Previous Comments:
On Tue, 24 Apr 2001, Rasmus Lerdorf wrote:
An easily reproducable segfault in a common PHP extension is a serious
issue which could lead to potential security breaches and thus lots of bad
mojo from nasty bugtraq postings. If we know about such a segfault and we
have a fix and go ahead and
I would like to see a timeout function implemented in PHP (something like
Perl's alarm function would be perfect). I notice there is a
set_time_limit() function in PHP, but it cannot be applied to a specified
block of code (it applies to the entire script) and it causes a fatal error
when the
An easily reproducable segfault in a common PHP extension is a serious
issue which could lead to potential security breaches and thus lots of bad
mojo from nasty bugtraq postings. If we know about such a segfault and we
have a fix and go ahead and release a stable package without this fix
I would like to see a timeout function implemented in PHP (something like
Perl's alarm function would be perfect). I notice there is a
set_time_limit() function in PHP, but it cannot be applied to a specified
block of code (it applies to the entire script) and it causes a fatal error
when
The QA process as it is IS a joke. Without the support from the developers
there aren't any possible ways that it can ever succeed.
It isn't the QA people who fix bugs. They just test and report to
developers
who should FIX those bugs. Some core developers seem to have forget this..
I can
I can agree more the amount of times I have approached developers to say
please fix this or what is the best way to get this fixed and just either
1) been ignored
2) told it doesnt matter
3) Told to fix it myself
4) In one extreme case (Ill leave the developer nameless) told its the users
That's not true. If you use register_shutdown_function() then this
function you register will be run once the timeout hits. See the chapter
in the manual on connection handling.
But this still doesn't let you apply a timeout to a specific block of code.
I am doing ad calls to a remote
Have you checked the bug database lately?
There are 43 open reports with bug type 'Reproducible crash'.
There are actually even more of them. I can easily reproduce
at least 10 bugs which cause segfaults. Those haven't been fixed yet.
Those haven't been fixed for a couple of releases now.
That's not true. If you use register_shutdown_function() then this
function you register will be run once the timeout hits. See the chapter
in the manual on connection handling.
But this still doesn't let you apply a timeout to a specific block of code.
I am doing ad calls to a remote
ID: 10312
Updated by: sterling
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Closed
Bug Type: Sablotron XSL
PHP Version: 4.0.4pl1
Assigned To:
Comments:
Can you try this with sabcmd (the sablotron executable). So
I can see whether or not this is a PHP extension problem (I
doubt it)
ID: 4787
User Update by: [EMAIL PROTECTED]
Old-Status: Closed
Status: Open
Bug Type: Reproduceable crash
Description: get_browser() still segments
With 4.0.5RC7 this still occurs, it only worked for the CVS at the time it was closed.
Its never worked before or since.
I can also recreate this
From: [EMAIL PROTECTED]
Operating system: Solaris 2.6
PHP version: 4.0.4pl1
PHP Bug Type: Apache related
Bug description: httpd -l gives mod_php4.c not compatible w/ 1.3.19
There seems to be an error with apache/php4
bin/httpd -l
httpd: module mod_php4.c is not compatible
ID: 10481
Updated by: rasmus
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Closed
Bug Type: Apache related
PHP Version: 4.0.4pl1
Assigned To:
Comments:
You compiled PHP against an older version of Apache and you are now trying to load it
into a newer one. Recompile your PHP against
ID: 10306
Updated by: sterling
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Closed
Bug Type: Sablotron XSL
PHP Version: 4.0 Latest CVS (12/04/2001)
Assigned To:
Comments:
Well if it stopped, then I'll mark the bug as closed. If
starts happening again, or you have more information,
ID: 8412
Updated by: sterling
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Closed
Bug Type: Sablotron XSL
PHP Version: 4.0.4
Assigned To: sterling
Comments:
Ok, try it and re-open the report if it happens. I've used
MySQL and Sablotron together fine...
Previous Comments:
On Tue, Apr 24, 2001 at 10:50:36AM +0200, Andi Gutmans wrote:
It definitely seems as if the logic in the code (filestat.c) is kind of
screwed up.
If no one has time to look at it I can try and take a look at it later on.
Andi
At 01:35 AM 4/24/2001 -0500, J. Jones wrote:
Forgive me for
Hi,
I have tracked down the bug in ./ext/interbase/interbase.c. I have
posted the bugfix on the web-site as a diff between version 1.48 and
the fixed version. Also bug #9257 has been identified and fixed.
The diff has been posted under _bug_-report #10458 :-)
Yours sincerely,
Lars Westermann
ID: 10082
Updated by: sterling
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Closed
Bug Type: cURL related
PHP Version: 4.0 Latest CVS (30/03/2001)
Assigned To:
Comments:
Changes incorporated in CVS, thanks.
Previous Comments:
Right, but when you are doing network work like this you should be using
fsockopen() directly which does have timeout support. readfile() with a
url argument just does a simple fsockopen anyway and issues a GET request.
Trivial to do yourself using fsockopen() and fputs() and this way you
Right, but when you are doing network work like this you should be using
fsockopen() directly which does have timeout support. readfile() with a
url argument just does a simple fsockopen anyway and issues a GET request.
Trivial to do yourself using fsockopen() and fputs() and this way
Personally, I think having an alarm (timeout) function is a really good
idea.
Setting a timer, and then being able to jump from whatever you are doing if
it is taking too long is something that has helped me do some really neat
stuff in C and Perl... and I was a little dissapointed when I
Andrei's Hebrew sure is getting better :)
At 21:15 24/4/2001, Andrei Zmievski wrote:
On Tue, 24 Apr 2001, Colin Viebrock wrote:
Parse error: parse error, expecting `T_PAAMAYIM_NEKUDOTAYIM' or `'('' in
/path/to/file.php on line 246
Zeev/Andi ... ? :)
Read expecting '::' or '('.
Personally, I think having an alarm (timeout) function is a really good
idea.
Setting a timer, and then being able to jump from whatever you are doing if
it is taking too long is something that has helped me do some really neat
stuff in C and Perl... and I was a little dissapointed when I
[Jason Sims [EMAIL PROTECTED]]
Personally, I think having an alarm (timeout) function is a really good
idea.
Setting a timer, and then being able to jump from whatever you are doing if
it is taking too long is something that has helped me do some really neat
stuff in C and Perl...
Perl uses SIGALRM to implement alarms, something which is not an option
when you're an Apache module.
Zeev
At 02:13 25/4/2001, Jason Sims wrote:
Personally, I think having an alarm (timeout) function is a really good
idea.
Setting a timer, and then being able to jump from whatever you
On Wed, 25 Apr 2001, Zeev Suraski wrote:
While I'd say Jani's letter was slightly over emotional ;), he does have a
point.
I think that taking a stop to look closely at the bugs database would be a
good thing, and the turn of a new version is a good time to do
it. Deciding 4.0.6 won't
From: [EMAIL PROTECTED]
Operating system: redhat 7.1
PHP version: 4.0.4pl1
PHP Bug Type: Filesystem function related
Bug description: if the filesize if more than 2GB, filesystem functions do not seem
to recognize
$folder = dir(.);
$folder-rewind() ;
clearstacache();
Zeev Suraski wrote:
Deciding 4.0.6 won't include any significant new features,
and that we'll start its release process after a bugs-database
-cleaning period sounds like a good idea to me.
So why restrict it to just the next release? It might make a lot of
sense to have an RC candidate
hi,
Maybe something like this
1. Any problems which result in seg faults/gpfs are show stoppers, code
doesnt
go out till its fixed, or feature is removed till we can fix it.
this is not correct (in general :) - there are segfaults in experimental
stuff that do not imply exploits, are no
From: [EMAIL PROTECTED]
Operating system: all
PHP version: 4.0.4
PHP Bug Type: Feature/Change Request
Bug description: someFunction() OR break;
why is the syntax
someFunction() OR anotherFunction();
only possible with a function on the right side of the OR? cause it has to
1)
I have now been adding functions to an extension initiated by ext_skel
for a couple of days
and familiarized myself with the source code layout and build
architecture.
It appears everything is controlled by the ../php4/configure file
which appears to be edited directly by ext_skel when it
At 02:24 AM 4/25/2001 +0300, Zeev Suraski wrote:
While I'd say Jani's letter was slightly over emotional ;), he does have a
point.
I think that taking a stop to look closely at the bugs database would be a
good thing, and the turn of a new version is a good time to do
it. Deciding 4.0.6 won't
ID: 9957
Updated by: sterling
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Closed
Bug Type: Compile Failure
PHP Version: 4.0 Latest CVS (23/03/2001)
Assigned To:
Comments:
fixed in cvs
Previous Comments:
---
Hi,
I just commited a patch which also cleaned up some other stuff (although it
could still use some fixing up).
Please check the latest CVS to see if it works now.
Also can you please check the lstat() command? I think it has the same
problem (I didn't fix it because I want to be sure) and I
From: [EMAIL PROTECTED]
Operating system: Win2000
PHP version: 4.0.4pl1
PHP Bug Type: ODBC related
Bug description: Problem with insert in ODBC
$BD = odbc_connect ('BdTest', SQL_CUR_USE_DRIVER);
$SQL = insert into test values ('a', 'b');
$TabUser = odbc_exec($BD, $SQL);
Andi Gutmans ([EMAIL PROTECTED]) wrote:
features (also because it has enough additional features already which are
enough for another minor version), but the developers need to actually go
through the bugs database and work on those crash bugs. It's not that easy
to get everyone to work on
Looking at the RC bugs graph:
http://master.debian.org/~wakkerma/bugs/
you'll see two precipitous drops in the number of RC bugs.
Those are bug parties.
- Steve
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
At 02:24 AM 4/25/2001 +0300, Zeev Suraski wrote:
While I'd say Jani's letter was slightly over emotional ;), he does have a
point.
I think that taking a stop to look closely at the bugs database would be a
good thing, and the turn of a new version is a good time to do
it. Deciding 4.0.6
On Wed, Apr 25, 2001 at 07:22:03AM +0200, Andi Gutmans wrote:
Hi,
I just commited a patch which also cleaned up some other stuff (although it
could still use some fixing up).
Please check the latest CVS to see if it works now.
Also can you please check the lstat() command? I think it has
Oh.. the readlink () function works fine in both instances..
readlink passed: /bin/false
readlink passed: /this/file/does/not/exist
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact
I have now been adding functions to an extension initiated by ext_skel
for a couple of days
and familiarized myself with the source code layout and build
architecture.
It appears everything is controlled by the ../php4/configure file
which appears to be edited directly by ext_skel when it
At 10:35 PM 4/24/2001 -0700, Rasmus Lerdorf wrote:
At 02:24 AM 4/25/2001 +0300, Zeev Suraski wrote:
While I'd say Jani's letter was slightly over emotional ;), he does have a
point.
I think that taking a stop to look closely at the bugs database would be a
good thing, and the turn of a
I commited another fix.
is_link() should work correctly now. If things have improved and you have
problems with lstat() and filetype() (which I think there's a good chance
that they are screwed up) let me know.
Thanks,
Andi
At 12:43 AM 4/25/2001 -0500, J. Jones wrote:
On Wed, Apr 25, 2001 at
On Tue, Apr 24, 2001 at 03:57:05PM -0400, Jon Parise wrote:
On Tue, Apr 24, 2001 at 08:31:26PM +0200, Thies C. Arntzen wrote:
[workaround snipped]
the problem here a cyclic references _and_ $this _not_ being
the instantiated object (unless u use this ugly ampersand
hack as
The readlink() function? You mean the is_link() function no?
The readlink() function is something completely different.
Can you also try those other two functions? lstat() and filetype()?
Andi
At 12:48 AM 4/25/2001 -0500, J. Jones wrote:
Oh.. the readlink () function works fine in both
On Wed, Apr 25, 2001 at 08:56:47AM +0200, Andi Gutmans wrote:
I commited another fix.
is_link() should work correctly now. If things have improved and you have
problems with lstat() and filetype() (which I think there's a good chance
that they are screwed up) let me know.
Thanks,
Andi
The question right now is how to best implement this. Do we add something
to the bug database to flag bugs in some manner and have a release
candidate summary page?
Or do we separate it out of the bug database and maintain the list
manually?
OK, my opinion would be to put a copy of the
At 11:04 PM 4/24/2001 -0700, Rasmus Lerdorf wrote:
Having a better defined/reproduced list of bugs is a must and if the QA
team can do that PHP will definitely benefit from it. However, today when
they ask people to fix bugs they are often not fixed and I don't even think
that they are
From: [EMAIL PROTECTED]
Operating system: HP-UX 11
PHP version: 4.0.4pl1
PHP Bug Type: Scripting Engine problem
Bug description: no input file specified when running as a CGI
I am running PHP4 4.0.4pl1 on HP-UX11 (64 bit) and
Apache 1.3.11. I compiled PHP4 with gcc and did
98 matches
Mail list logo
