ID: 10578
User Update by: [EMAIL PROTECTED]
Status: Open
Bug Type: Scripting Engine problem
Description: Serious: Mac line-feeds not recognized as linefeeds in code any more
Andi Gutmans has fixed this bug through changes to
Zend/zend_language_scanner.l and Zend/zend_ini_scanner.l
Previous
On Wed, 02 May 2001 23:25:36 +0200, Andi Gutmans [EMAIL PROTECTED] wrote:
Attached is a patch which should allow the scripting engine to also
allow \r as line delimiters.
Thanks; it works. Bug #10578 has been closed.
If someone on Mac OS X who has had
problems can test this and send me
ID: 10578
User Update by: [EMAIL PROTECTED]
Old-Status: Open
Status: Closed
Bug Type: Scripting Engine problem
Description: Serious: Mac line-feeds not recognized as linefeeds in code any more
Previous Comments:
---
ID: 10618
Updated by: sniper
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Bogus
Bug Type: *General Issues
PHP Version: 4.0.5
Assigned To:
Comments:
This is not PHP bug. Zend is a commercial company
which provides this extension. Ask them for updated one.
--Jani
Previous
ID: 10621
Updated by: sniper
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Feedback
Bug Type: Dynamic loading
PHP Version: 4.0.5
Assigned To:
Comments:
open - feedback
(fmk: TRY to remember this..)
Previous Comments:
ID: 10622
Updated by: sniper
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Feedback
Bug Type: PostgreSQL related
PHP Version: 4.0.5
Assigned To:
Comments:
Can you please tell how you concluded that his function
doesn't exist? As I look at the sources now, it clearly
IS there. When
ID: 10624
Updated by: hholzgra
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Bogus
Bug Type: MySQL related
PHP Version: Earlier? Upgrade first!
Assigned To:
Comments:
so the php-3.0.12-6.rpm just doesn't seem to have
mySQL support compiled in
this is not a php error, blame RedHat
This is the message that I get:
Warning: This compilation does not support pg_cmdtuples() in
c:\cygwin\usr\local\www\generic\lib\phplib\db_pgsql.inc on line 146
The php_pgsql.dll I got from the Win32 PHP 4.0.5 ZIP. It has the following
stamp:
Created: Tuesday, 20 March 2001, 10:44:50 AM
ID: 10627
Updated by: sniper
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Feedback
Bug Type: Sockets related
PHP Version: 4.0.5
Assigned To:
Comments:
Works for me with latest CVS on Linux just fine.
There have been some fixes in sockets extension since
4.0.5 so please try the
ID: 10458
Updated by: sniper
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Closed
Bug Type: InterBase related
PHP Version: 4.0.4pl1
Assigned To:
Comments:
Andi applied your patch.
--Jani
Previous Comments:
ID: 9257
Updated by: sniper
Reported By: [EMAIL PROTECTED]
Old-Status: Assigned
Status: Closed
Bug Type: InterBase related
PHP Version: 4.0.4pl1
Assigned To: jah
Comments:
This should be fixed in CVS now.
--Jani
Previous Comments:
On Thu, 3 May 2001, Alexander Bokovoy wrote:
This code branch should only be triggered if HAVE_IMAP_SSL is defined, which
should only happen if you configure php --with-imap-ssl. If you're doing so,
it's assumed that you've built c-client with SSL support.
Current configure macros in PHP
ID: 10292
Updated by: sniper
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Closed
Bug Type: InterBase related
PHP Version: 4.0.4pl1
Assigned To:
Comments:
Should be fixed in CVS now.
--Jani
Previous Comments:
The attachment has some warnings that occurred during a compile
on MacOS X. Not anything fatal but annoying.
--Jani
In file included from /usr/include/httpd/httpd.h:72,
from sapi_apache.c:32:
/usr/include/httpd/ap_config.h:425: warning: `HAVE_MMAP' redefined
On Thu, May 03, 2001 at 09:28:03AM +0200, Jani Taskinen wrote:
On Thu, 3 May 2001, Alexander Bokovoy wrote:
This code branch should only be triggered if HAVE_IMAP_SSL is defined, which
should only happen if you configure php --with-imap-ssl. If you're doing so,
it's assumed that you've
On Thu, May 03, 2001 at 09:28:03AM +0200, Jani Taskinen wrote:
On Thu, 3 May 2001, Alexander Bokovoy wrote:
This code branch should only be triggered if HAVE_IMAP_SSL is defined, which
should only happen if you configure php --with-imap-ssl. If you're doing so,
it's assumed that you've
From: [EMAIL PROTECTED]
Operating system: Linux (Debian Sid)
PHP version: 4.0.5
PHP Bug Type: Apache related
Bug description: request_config is bogus
Using apache 1.3.19-1 and php4.0.4.5rc6-2 (debian packages)
$ ./ext_skel --extname=apdebug
Apply this patch:
diff -ur
From: [EMAIL PROTECTED]
Operating system: Windows
PHP version: 4.0.5
PHP Bug Type: Feature/Change Request
Bug description: SMTP: mail() the fifth parameter
It will be real handy if ...
mail() allows smtp specification in the new fifth parameter of mail()
mail([EMAIL
ID: 10629
User Update by: [EMAIL PROTECTED]
Status: Open
Bug Type: Feature/Change Request
Description: SMTP: mail() the fifth parameter
It will be real handy if ...
mail() allows smtp specification in the new fifth parameter of mail()
mail([EMAIL PROTECTED],
the subject,
$message,
From:
On Thu, 3 May 2001, Alexander Bokovoy wrote:
You're both wrong. This is really a bug in the IMAP-2001.beta sources.
It's not possible to build it with SSL support on Unix.
It is possible and I did it, and it works. That's why I'm saying about it.
Look closer to the circumstances where this
And you expect us to give you that power? :)
Seriously, PHP isn't going to start following Nazi-like strict rules. We
shouldn't get into jurisdictions and stuff like that because they're
endless discussions with no point. In an opensource project you can set
guidelines, not laws, and we
On Thu, May 03, 2001 at 10:43:21AM +0200, Jani Taskinen wrote:
On Thu, 3 May 2001, Alexander Bokovoy wrote:
You're both wrong. This is really a bug in the IMAP-2001.beta sources.
It's not possible to build it with SSL support on Unix.
It is possible and I did it, and it works. That's
This is known bug since early March but nobody fixed it and in general
fixing requires serious rework of PHP4's configure macros concept.
I plan to address this by introducing two new macros which
can embrace the sections which contain optional
PHP_ARG_WITH/PHP_ARG_ENABLE macros.
On Thu, May 03, 2001 at 10:43:21AM +0200, Jani Taskinen wrote:
On Thu, 3 May 2001, Alexander Bokovoy wrote:
You're both wrong. This is really a bug in the IMAP-2001.beta sources.
It's not possible to build it with SSL support on Unix.
It is possible and I did it, and it works. That's
On Thu, May 03, 2001 at 10:54:19AM +0200, Sascha Schumann wrote:
This is known bug since early March but nobody fixed it and in general
fixing requires serious rework of PHP4's configure macros concept.
I plan to address this by introducing two new macros which
can embrace the
Stig Sæther Bakken wrote:
I couldn't find any news on PHP Kongress 2001, have you found someone
to organize it yet (from the little German I know I think that's what
the web page said at least)?
Yes, an organizer was found. A press release about there where, when,
etc. should be out in
On Thu, 3 May 2001, Zeev Suraski wrote:
And you expect us to give you that power? :)
Did I suggest that? I didn't. I was referring only to
the rest of that piece of text, not the part about 'giving power'.
Seriously, PHP isn't going to start following Nazi-like strict rules. We
shouldn't get
* Sebastian Bergmann wrote:
Yes, an organizer was found. A press release about there where, when,
etc. should be out in about two weeks, AFAIK. Björn?
Yes. We decided for the great Software Support Verlag
who is responsible for the german speaking magazine
LinuxEnterprise, many books
On Thu, 3 May 2001, Alexander Bokovoy wrote:
IMAP-2001.beta doesn't work but it doesn't even matter as it still is _beta_.
As original author already pointed out, error triggers out with IMAP
2000*, not with IMAP 2001 betas. And I'm saying about it too. With
Please read that bug report. It
On Thu, 3 May 2001, Sascha Schumann wrote:
On Thu, 3 May 2001, Jani Taskinen wrote:
Amen. There can't be _ANY_ exceptions to this. Not even Sascha or ANYBODY
else. Including Zeev/Andi/Rasmus. Just thinking of that FastCGI thingie..
Funny that you mention my name as the first one in
At 11:08 AM 5/3/2001 +0200, Sascha Schumann wrote:
On Thu, 3 May 2001, Jani Taskinen wrote:
On Wed, 2 May 2001, Steve Langasek wrote:
Give the QA team that power. Let the release branch be reserved
exclusively
for bugfixes, and give the QA team control over what gets committed to the
On Thu, 3 May 2001, Alexander Bokovoy wrote:
Hrhm. If you know what is wrong then fix it and send a patch.
Or at least point us WHERE the problem is. Everything works
for me just fine as it is - no broken functionality.
So, it means that you never test PHP extensions in SCE mode.
So? I have
Jani Taskinen wrote:
IMAP-2000 ext/imap does not compiles well using phpize because both
PHP_ARG_WITH() in its config.m4.
Why would anyone want to use phpize on imap extension?
(forgive me but I never have needed phpize..)
You do when you want to develop self-contained extensions. SCEs
On Thu, May 03, 2001 at 11:19:10AM +0200, Jani Taskinen wrote:
On Thu, 3 May 2001, Alexander Bokovoy wrote:
IMAP-2001.beta doesn't work but it doesn't even matter as it still is _beta_.
As original author already pointed out, error triggers out with IMAP
2000*, not with IMAP 2001 betas.
Jani Taskinen wrote:
So, it means that you never test PHP extensions in SCE mode.
So? I have no use for SCEs.
All the world, fall in line with Jani. Some people do need them.
For PHP too, see package argument earlier.
Emile
--
PHP Development Mailing List http://www.php.net/
To
On Thu, May 03, 2001 at 11:21:28AM +0200, Jani Taskinen wrote:
On Thu, 3 May 2001, Alexander Bokovoy wrote:
Hrhm. If you know what is wrong then fix it and send a patch.
Or at least point us WHERE the problem is. Everything works
for me just fine as it is - no broken functionality.
So,
In an effort to stop a long going ping-pong again, let's concentrate on
figuring out what was wrong with the old release, and trying to improve it
in the future.
I'll start by saying that generally, overall, the last release was pretty
good. Ok, so COM didn't work, but only a very small
[Zeev Suraski [EMAIL PROTECTED]]
In an effort to stop a long going ping-pong again, let's concentrate
on figuring out what was wrong with the old release, and trying to
improve it in the future.
I'll start by saying that generally, overall, the last release was
pretty good. Ok, so COM
On Thu, 3 May 2001, Emiliano wrote:
Jani Taskinen wrote:
Why would anyone want to use phpize on imap extension?
(forgive me but I never have needed phpize..)
You do when you want to develop self-contained extensions. SCEs are
useful for large PHP extensions that have to live outside the main
ID: 10622
Updated by: dbeu
Reported By: [EMAIL PROTECTED]
Old-Status: Feedback
Status: Closed
Bug Type: PostgreSQL related
PHP Version: 4.0.5
Assigned To:
Comments:
it *is* fixed in the cvs, but 4.0.5 was branched before that change was commited.
Previous Comments:
At 05:52 AM 5/3/2001 -0400, Stig Sæther Bakken wrote:
We'll always have the problem of I need to MFH this, pretty please,
but I think that started working well at the end of the 4.0.5 QA. :-)
I actually also think that on a whole 4.0.5's release process was pretty
good and a big improvement on
ID: 10621
Updated by: dbeu
Reported By: [EMAIL PROTECTED]
Old-Status: Feedback
Status: Closed
Bug Type: Dynamic loading
PHP Version: 4.0.5
Assigned To:
Comments:
4.0.5 's php_gd.dll works perfectly...
Previous Comments:
On Thu, 3 May 2001, Alexander Bokovoy wrote:
On Thu, May 03, 2001 at 11:21:28AM +0200, Jani Taskinen wrote:
On Thu, 3 May 2001, Alexander Bokovoy wrote:
Hrhm. If you know what is wrong then fix it and send a patch.
Or at least point us WHERE the problem is. Everything works
for me just
From: [EMAIL PROTECTED]
Operating system:
PHP version: 4.0 Latest CVS (03/05/2001)
PHP Bug Type: *Install and Config
Bug description: i can't delete on my website (in the header) this words
content-type:
--
Edit Bug report at: http://bugs.php.net/?id=10630edit=1
--
ID: 10579
Updated by: dbeu
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Closed
Bug Type: Compile Failure
PHP Version: 4.0.5
Assigned To:
Comments:
remove the damn cygwin libaries from your include path you don't need them.
please also note that the single threaded php version is
ID: 10630
Updated by: sniper
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Bogus
Bug Type: *Install and Config
PHP Version: 4.0 Latest CVS (03/05/2001)
Assigned To:
Comments:
not enough info
Previous Comments:
From: [EMAIL PROTECTED]
Operating system: Linux 2.2.14
PHP version: 4.0.4pl1
PHP Bug Type: Scripting Engine problem
Bug description: Incorrectly reported line number on errors with Mac line-breaks
When a file is saved using Macintosh-style line breaks
('\r') and there is
Andi wrote:
That brings me to more current events. I'd like to roll an RC1 for 4.0.6
pretty soon (Saturday?).
I don't want to slow things down here, and if Saturday can be achieved, all
well and good, but we perhaps ought to have a strong guideline that, say, 1
weeks warning of an impending RC
ID: 10619
Updated by: dbeu
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Closed
Bug Type: Apache related
PHP Version: 4.0.5
Assigned To:
Comments:
unable to repsoduce in the same environment.
i guess you haven't replaced everything with the new build.
Previous Comments:
At 11:16 AM 5/3/2001 +0100, Phil Driscoll wrote:
Andi wrote:
That brings me to more current events. I'd like to roll an RC1 for 4.0.6
pretty soon (Saturday?).
I don't want to slow things down here, and if Saturday can be achieved, all
well and good, but we perhaps ought to have a strong
ID: 10631
Updated by: derick
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Feedback
Bug Type: Scripting Engine problem
PHP Version: 4.0.4pl1
Assigned To:
Comments:
This is likely fixed in the CVS now. PHP 4.0.6 will have it. Can you please try the
latest CVS of PHP (and Zend) to test
Can we drop this issue already? Sascha said his working on it, okay?
FYI: I'm not the maintainer of IMAP extension. Check EXTENSIONS file.
--Jani
On Thu, 3 May 2001, Emiliano wrote:
Jani Taskinen wrote:
You do when you want to develop self-contained extensions. SCEs are
useful for large
On Thu, 3 May 2001, Phil Driscoll wrote:
Andi wrote:
That brings me to more current events. I'd like to roll an RC1 for 4.0.6
pretty soon (Saturday?).
I don't want to slow things down here, and if Saturday can be achieved, all
well and good, but we perhaps ought to have a strong guideline that,
Zeev,
do you think ASF is a Nazi-like group? I don't think so.
Nor do I witness endless discussions caused by the fact that
the Apache release cycle is far (in a galaxy far, far away.. :)
stricter than the PHP one.
4.0.5 took very long to release, and it seems like it could
have been released
ID: 10631
User Update by: [EMAIL PROTECTED]
Old-Status: Feedback
Status: Open
Bug Type: Scripting Engine problem
Description: Incorrectly reported line number on errors with Mac line-breaks
Thanks, but unfortunately I can't test it myself as my servers have no C compilation
facilities (for
ID: 10631
Updated by: andi
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Closed
Bug Type: Scripting Engine problem
PHP Version: 4.0.4pl1
Assigned To:
Comments:
Should be fixed in 4.0.6.
Please open a new bug report if the problem persists with 4.0.6
Previous Comments:
At 12:48 3.5. 2001, Andi Gutmans wrote the following:
--
At 12:47 PM 5/3/2001 +0200, Cynic wrote:
Zeev,
do you think ASF is a Nazi-like group? I don't think so.
Nor do I witness endless discussions caused by the fact that
the Apache
On Thu, 3 May 2001, Andi Gutmans wrote:
At 12:47 PM 5/3/2001 +0200, Cynic wrote:
Is it? I'm not that sure. They also release with known bugs although I
admit to not knowing their exact release cycle so I won't comment more on
Ehem. We release with known bugs too but we don't tell it to anyone..
What's the status of the show stoppers list James put up? We should fix as
many bugs as we can (at least those which are planned to be fixed in 4.0.6)
before branching, to avoid having to synchronize two branches for every bug
fix.
Zeev
At 13:04 3/5/2001, Andi Gutmans wrote:
At 05:52 AM
At 13:47 3/5/2001, Cynic wrote:
Zeev,
do you think ASF is a Nazi-like group? I don't think so.
Nor do I witness endless discussions caused by the fact that
the Apache release cycle is far (in a galaxy far, far away.. :)
stricter than the PHP one.
I was talking about the ruleset and the way to
At 13:27 3/5/2001, Jani Taskinen wrote:
I just want to remind everyone that the 4.0.6 is suppose to have mainly
bug fixes..or wasn't this agreed on yet?
Yes it was.
Zeev
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
ID: 10342
Updated by: cynic
Reported By: [EMAIL PROTECTED]
Old-Status: Closed
Status: Open
Bug Type: Compile Problem
PHP Version: 4.0 Latest CVS (11/04/2001)
Assigned To:
Comments:
well, CVS might convert LF to CRLF, but the fact is, that TSRM.dsp in snapshots from
snaps.php.net has had LF for
What's the status of the show stoppers list James put up? We
should fix as
many bugs as we can (at least those which are planned to be fixed
in 4.0.6)
before branching, to avoid having to synchronize two branches for
every bug
fix.
Ill go through tonight and update list and post
At 12:52 PM 5/3/2001 +0100, James Moore wrote:
What's the status of the show stoppers list James put up? We
should fix as
many bugs as we can (at least those which are planned to be fixed
in 4.0.6)
before branching, to avoid having to synchronize two branches for
every bug
fix.
What's the status of the show stoppers list James put up? We
should fix as
many bugs as we can (at least those which are planned to be fixed
in 4.0.6)
before branching, to avoid having to synchronize two branches for
every bug
fix.
Ill go through tonight and update list
At 12:58 PM 5/3/2001 +0100, James Moore wrote:
What's the status of the show stoppers list James put up? We
should fix as
many bugs as we can (at least those which are planned to be fixed
in 4.0.6)
before branching, to avoid having to synchronize two branches for
every
[Andi Gutmans [EMAIL PROTECTED]]
At 05:52 AM 5/3/2001 -0400, Stig Sæther Bakken wrote:
We'll always have the problem of I need to MFH this, pretty please,
but I think that started working well at the end of the 4.0.5 QA. :-)
I actually also think that on a whole 4.0.5's release process was
ID: 10626
Updated by: cynic
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Bogus
Bug Type: PCRE related
PHP Version: 4.0.5
Assigned To:
Comments:
You escaped the $1000 on the PHP level, so literal $1000 was sent to PCRE, where $10
was interpreted as a backreference, and since there
Hi Andi,
I just spotted a bug report that confirms this on w98:
http://bugs.php.net/?id=10623edit=1
At 13:21 2.5. 2001, Andi Gutmans wrote the following:
--
Sounds like a bug in PHP to me.
Andi
At 01:00 PM 5/2/2001 +0200, Cynic
ID: 10631
User Update by: [EMAIL PROTECTED]
Old-Status: Closed
Status: Open
Bug Type: Scripting Engine problem
Description: Incorrectly reported line number on errors with Mac line-breaks
Thanks, but unfortunately I can't test it myself as my servers have no C compilation
facilities (for
ID: 10631
User Update by: [EMAIL PROTECTED]
Status: Open
Bug Type: Scripting Engine problem
Description: Incorrectly reported line number on errors with Mac line-breaks
Thanks, but unfortunately I can't test it myself as my servers have no C compilation
facilities (for security purposes, etc.),
[Oyvind Moll [EMAIL PROTECTED]]
* Stig Sæther Bakken [EMAIL PROTECTED]
|
| sunday's morning paper in Trondheim
That won't be much of a name.
(...or has Adresseavisa started printing a Sunday edition?)
That was of course supposed to be saturday. :-)
- Stig
--
Stig Sæther Bakken
At 11:49 03.05.2001 +, [EMAIL PROTECTED] wrote:
ID: 10342
Updated by: cynic
Reported By: [EMAIL PROTECTED]
Old-Status: Closed
Status: Open
Bug Type: Compile Problem
PHP Version: 4.0 Latest CVS (11/04/2001)
Assigned To:
Comments:
well, CVS might convert LF to CRLF, but the fact is, that
ID: 10631
Updated by: derick
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Closed
Bug Type: Scripting Engine problem
PHP Version: 4.0.4pl1
Assigned To:
Comments:
should be fixed in 4.0.6.
Please open a new bug report if the problem persists with 4.0.6
Previous Comments:
all other ds[pw] files have CRLF. I think it should be fixed.
At 14:30 3.5. 2001, Daniel Beulshausen wrote the following:
--
At 11:49 03.05.2001 +, [EMAIL PROTECTED] wrote:
ID: 10342
Updated by: cynic
Reported By: [EMAIL PROTECTED]
On Wed, May 02, 2001 at 11:14:38PM +0300, Zeev Suraski wrote:
At 23:06 2/5/2001, Troels Arvin wrote:
Note that there was no such problem with PHP 4.0.4pl1 and earlier.
That's very odd, as PHP never considered \r alone to be a linefeed...
IIRC, Mac's use \r as an end-of-line. They don't
On Thu, 03 May 2001, Zeev Suraski wrote:
At 13:27 3/5/2001, Jani Taskinen wrote:
I just want to remind everyone that the 4.0.6 is suppose to have mainly
bug fixes..or wasn't this agreed on yet?
Yes it was.
Does that mean I should take my array_map() and array_filter() functions
out? ;-)
At 08:35 AM 5/3/2001 -0500, Andrei Zmievski wrote:
On Thu, 03 May 2001, Zeev Suraski wrote:
At 13:27 3/5/2001, Jani Taskinen wrote:
I just want to remind everyone that the 4.0.6 is suppose to have mainly
bug fixes..or wasn't this agreed on yet?
Yes it was.
Does that mean I should take
On Thu, 03 May 2001, Andi Gutmans wrote:
Nah but I think it means that you shouldn't add any more array_foobar()
functions before 4.0.7-dev :)
Geez, just when I finished array_foobar()..
By the way, what happened to that array_defined() or whatever function
which was added? Didn't we say
At 08:45 AM 5/3/2001 -0500, Andrei Zmievski wrote:
On Thu, 03 May 2001, Andi Gutmans wrote:
Nah but I think it means that you shouldn't add any more array_foobar()
functions before 4.0.7-dev :)
Geez, just when I finished array_foobar()..
:)
By the way, what happened to that
On Thu, 03 May 2001, Andi Gutmans wrote:
key_exists(), you mean? I didn't put it in, and as far as I know it's
still there.
I'd really like to nuke it.
I can sort of see his point really, if $array['foo'] = NULL there is no
way to know whether key 'foo' exists or not..
-Andrei
* Power
At 16:46 3/5/2001, Andi Gutmans wrote:
By the way, what happened to that array_defined() or whatever function
which was added? Didn't we say it should be nuked? isset() and empty() are
enough IMO especially as NULL is used as undefined.
key_exists(), you mean? I didn't put it in, and as
At 08:48 AM 5/3/2001 -0500, Andrei Zmievski wrote:
On Thu, 03 May 2001, Andi Gutmans wrote:
key_exists(), you mean? I didn't put it in, and as far as I know it's
still there.
I'd really like to nuke it.
I can sort of see his point really, if $array['foo'] = NULL there is no
way to know
On Thu, 03 May 2001, Andi Gutmans wrote:
Yeah but I'm afraid it'll make scripts be written on behavior which
shouldn't be counted on.
Maybe in future versions of Zend $array['foo'] won't be defined. There are
certain situations where I think it was impossible to not define it so it
was
From: [EMAIL PROTECTED]
Operating system: Linux
PHP version: 4.0.5
PHP Bug Type: MySQL related
Bug description: MySQL port broken
The mylsq module is broken because the default port/path is wrong for localhosts.
Can be solved by specifying them in php.ini, but this was not
At 08:53 AM 5/3/2001 -0500, Andrei Zmievski wrote:
On Thu, 03 May 2001, Andi Gutmans wrote:
Yeah but I'm afraid it'll make scripts be written on behavior which
shouldn't be counted on.
Maybe in future versions of Zend $array['foo'] won't be defined. There are
certain situations where I
Err, as you say, PHP should make things easy. I don't see how
making tell NULL from an undefined variable makes anything
easier.
At 15:49 3.5. 2001, Andi Gutmans wrote the following:
--
At 08:48 AM 5/3/2001 -0500, Andrei Zmievski
Hmmm, looks like the MySQL module was changed to add NULL elements to the
array. It even looks as if you changed it :)
I intentionally removed the code that populated return values with NULL's,
to avoid inconsistencies. People should use the mysql_fetch_field() to
check which fields there
ID: 10632
Updated by: derick
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Closed
Bug Type: MySQL related
PHP Version: 4.0.5
Assigned To:
Comments:
Alread fixed in CVS
Previous Comments:
---
[2001-05-03
On Thu, 03 May 2001, Zeev Suraski wrote:
Hmmm, looks like the MySQL module was changed to add NULL elements to the
array. It even looks as if you changed it :)
I intentionally removed the code that populated return values with NULL's,
to avoid inconsistencies. People should use the
insert impossible somewhere in the sentence to make it
make sense.
At 16:04 3.5. 2001, Cynic wrote the following:
--
Err, as you say, PHP should make things easy. I don't see how
making tell NULL from an undefined variable makes
ID: 10619
User Update by: [EMAIL PROTECTED]
Old-Status: Closed
Status: Open
Bug Type: Apache related
Description: Apache is not able to load the php module
I tried again, and here are the steps that I took:
1) I uninstalled and removed all files for both PHP and Apache.
2) I unzipped PHP
If we are to do this then we should definatly separate the distributions
and
the actual scripts, could we make phpweb_scripts phpweb_dist if somtone
checksout phpweb then they get both byt we can also get phpweb_scripts
separately. (cvs cando this automatically)
Agreed.
The phpweb tree
From: [EMAIL PROTECTED]
Operating system: linux
PHP version: 4.0.4
PHP Bug Type: *Programming Data Structures
Bug description: settype(.., double) not work as expected(or documented)
$tmp = 111t11t;
settype($tmp, double);
echo $tmp;
returns '111' imho it should be
I very much agree with Andrei on this. Please, keep the
existing functionality.
Although, I'm not familiar with any issues possibly connected
with this. Does it hurt anything?
At 16:03 3.5. 2001, Andrei Zmievski wrote the following:
At 17:20 3/5/2001, Cynic wrote:
I very much agree with Andrei on this. Please, keep the
existing functionality.
Although, I'm not familiar with any issues possibly connected
with this. Does it hurt anything?
Yes, it requires adding of functions that duplicate isset()'s behavior in a
way that
On Thu, 03 May 2001, Zeev Suraski wrote:
Yes, it requires adding of functions that duplicate isset()'s behavior in a
way that may change in the future (implementation dependent).
What do you mean? You won't be able to store NULL's in the arrays?
-Andrei
* I don't mind going nowhere as long
From: [EMAIL PROTECTED]
Operating system: Linux 2.4.2
PHP version: 4.0.4pl1
PHP Bug Type: Scripting Engine problem
Bug description: #2293 related: to many Slashes s.t.
Hi,
sometimes strings from a DB or a textfile are added with backslashes all over one
page. if you
On Thu, 3 May 2001, Zeev Suraski wrote:
At 17:20 3/5/2001, Cynic wrote:
I very much agree with Andrei on this. Please, keep the
existing functionality.
Although, I'm not familiar with any issues possibly connected
with this. Does it hurt anything?
Yes, it requires adding of functions that
At 10:43 AM 5/3/2001 -0400, Joe Brown wrote:
What about an isnull() function, opposed to key_exists();
IsPossible()?
Yeah that's definitely a possiblity but then you'd have to do something like.
if (isset($a[foo]) || isnull($a[foo))
Kind of sucky.
But we should think of a good resolution for a
1 - 100 of 236 matches
Mail list logo
