php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #8180 Multiple "else" clauses in an "if" statement do not generate an error
Submitted: 2000-12-08 19:23 UTC Modified: 2000-12-08 20:47 UTC
From: greg at adhesivemedia dot com Assigned:
Status: Closed Package: Scripting Engine problem
PHP Version: 4.0.3pl1 OS: Winnt 4.0 sp6
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem:
27 + 29 = ?
Subscribe to this entry?

 
 [2000-12-08 19:23 UTC] greg at adhesivemedia dot com
The following script does not generate a parse error, and results in either zero output (an empty document), or a skeletal HTML document unrelated to the desired output (see below).

Sample script
----------------------------------------------
<?php

 if ( 1 ) {
  print("1");
 } else {
  print("2");
 } else {
  print("3");
 }

?>
----------------------------------------------


Weird HTML output
----------------------------------------------
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=windows-1252"></HEAD>
<BODY></BODY></HTML>
----------------------------------------------
(note: this HTML output is unrelated to any code in the php file. It appears to be coming from the script engine itself?)

The expecetd behavior would be that an error is generated by the script engine. This proved to be an irritating bug to track down on a fairly complex page with multiple nested "if" statements, since no error was reported and no content was generated.

One other note, this same sample file generates a parse error on our FreeBSD box running PHP 4.0.2.

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2000-12-08 19:50 UTC] sniper@php.net
This works just like it should, generates a parse error for me.
(I'm using the latest CVS)

Check your php.ini:

error_reporting = E_ALL

if it is something else, try changing to E_ALL.
And if it still doesn't generate an error, try PHP4.0.4RC4:
http://www.php.net/distributions/php-4.0.4RC4.tar.gz

--Jani
 [2000-12-08 20:47 UTC] sniper@php.net
User feedback:
------------
My mistake. Our NT server had:
error_reporting = E_COMPILE_ERROR|E_ERROR|E_CORE_ERROR
but our FreeBSD server had:
error_reporting = E_ALL & ~E_NOTICE

Now that I've re-configured the NT box, it's reporting the error just
fine...

 
PHP Copyright © 2001-2021 The PHP Group
All rights reserved.
Last updated: Wed Apr 14 06:01:24 2021 UTC