php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #19774 isset behaviour change 4.2.2 -> 4.2.3
Submitted: 2002-10-05 16:49 UTC Modified: 2002-10-05 18:21 UTC
From: andrusk at delfi dot ee Assigned:
Status: Not a bug Package: *General Issues
PHP Version: 4.2.3 OS: Solars 8 Sparc
Private report: No CVE-ID: None
View Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
If you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: andrusk at delfi dot ee
New email:
PHP Version: OS:

 

 [2002-10-05 16:49 UTC] andrusk at delfi dot ee 
Hi,
We are using apache 1.2.26, register_globals is on.
configure line:
./configure --with-oci8 --with-mysql=/usr/local/mysql --with-apache=../apache_1.3.26 --enable-track-vars --with-mcrypt --enable-gd-native-ttf --with-gd --with-jpeg-dir --with-png-dir=/usr/local --with-freetype-dir=/usr/local --with-zlib-dir=/usr --with-curl

Here is out test script, test php:
<?echo ":".isset($code).":";?>

with php 4.2.2
http://something/test.php?code
producec output:
::

with php 4.2.3
http://something/test.php?code
producec output:
:1:

It seems like isset behaviour changed from 4.2.2 to 4.2.3. This required changes into our application, I'd like to know if this behaviour changes again or will stay like it is with 4.2.3.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2002-10-05 17:08 UTC] neuman_peter at hotmail dot com 
Please Test:

<?php
echo ":".isset($code).":";
?>
 [2002-10-05 17:38 UTC] andrusk at delfi dot ee 
<?php des not make difference for me. In our app scripts we use ?php.

Anyway, the one I provided is just a test script to demonstrate this bug.
We have problem with our application and would like to know, if we should wait for php 4.2.4 or should we start changing and testing this application in order to accomodate this new behaviour.
 [2002-10-05 17:41 UTC] nicos@php.net 
It's not really a bug, its a new way to return things with this function. By the way I agree that it's not really a good thing that it changed.
 [2002-10-05 17:45 UTC] sesser@php.net 
Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to report
a bug at http://bugs.php.net/how-to-report.php


The behaviour in 4.2.3 is the correct one.
I would be very suprised if this breaks any scripts because
it was not working before, now it works.
 [2002-10-05 18:21 UTC] andrusk at delfi dot ee 
Well, it worked for me before, now I'm forced to change my code. So much for surprise. Well, this happens.

Thank you for your help. I believe I got my answer.
 
PHP Copyright © 2001-2025 The PHP Group
All rights reserved. 		Last updated: Fri Dec 05 10:00:01 2025 UTC