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

go to bug id or search bugs for

Bug #21499 include 'bogus'; refers to bogus function.main
Submitted: 2003-01-07 14:02 UTC Modified: 2003-01-07 20:45 UTC
Votes:1
Avg. Score:3.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:1 (100.0%)
Same OS:1 (100.0%)
From: philip at cornado dot com Assigned:
Status: Closed Package: Scripting Engine problem
PHP Version: 4.3.0 OS: all
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:
46 - 22 = ?
Subscribe to this entry?

 
 [2003-01-07 14:02 UTC] philip at cornado dot com 
<?php include 'foo' ?>

Warning: main(foo) [function.main]: 
  failed to create stream: No such file or directory in...

Warning: main() [function.main]: Failed opening 'foo' for inclusion (include_path='.') in...

Basically, this error could be a little nicer and in the very least link to function.include and not a non-existent function.main.

This is the case with all the include/require constructs.

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2003-01-07 17:36 UTC] iliaa@php.net 
Since include is not a function but rather a language construct this is unlikely to be ever fixed.
The error as is, imo is reasonably descriptive as it tells what action had failed and why.
 [2003-01-07 18:28 UTC] philip@php.net 
The fact that it provides two 404 links to a non-existent PHP function named main() is rather misleading and is not reasonable.  I didn't call/use any function named main(), I used include().  Fact is, include() could not include the file because the file could not be opened.  Simply "Failed opening foo for inclusion" is enough, like it used to be before php_error_docref.  Linking to function.include would be fine too.

IMHO this should remain open until someone fixes it.  I would put php_error_docref in the summary but I really don't know the internals or if that's the problem.
 [2003-01-07 20:45 UTC] iliaa@php.net 
This bug has been fixed in CVS.

In case this was a PHP problem, snapshots of the sources are packaged
every three hours; this change will be in the next snapshot. You can
grab the snapshot at http://snaps.php.net/.
 
In case this was a documentation problem, the fix will show up soon at
http://www.php.net/manual/.

In case this was a PHP.net website problem, the change will show
up on the PHP.net site and on the mirror sites in short time.
 
Thank you for the report, and for helping us make PHP better.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Thu Apr 18 12:01:28 2024 UTC