Re: [PHP-DEV] PHP 4.0 Bug #1531 Updated: require() causes flex scanner error

[Zeev Suraski]

Well it's not a bug - it's already caught in the PHP error system, you can 
manipulate it, etc.  Someone can improve the error message if they wish...

Zeev

At 20:56 10/2/2001, Hartmut Holzgraefe wrote:
>[EMAIL PROTECTED] wrote:
> > intended behavior
>
>so it's intended behaviour to give confusing error messages? :)
>
>--
>Hartmut Holzgraefe  [EMAIL PROTECTED]  http://www.six.de  +49-711-99091-77
>
>Besuchen Sie uns auf der CeBIT 2001 - in Halle 6 Stand F62/4

--
Zeev Suraski <[EMAIL PROTECTED]>
CTO &  co-founder, Zend Technologies Ltd. http://www.zend.com/


-- 
PHP Development Mailing List 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Re: [PHP-DEV] PHP 4.0 Bug #1531 Updated: require() causes flex scanner error

[Hartmut Holzgraefe]

[EMAIL PROTECTED] wrote:
> intended behavior

so it's intended behaviour to give confusing error messages? :) 

-- 
Hartmut Holzgraefe  [EMAIL PROTECTED]  http://www.six.de  +49-711-99091-77 

Besuchen Sie uns auf der CeBIT 2001 - in Halle 6 Stand F62/4

-- 
PHP Development Mailing List 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Re: [PHP-DEV] PHP 4.0 Bug #1531 Updated: require() causes flex scanner error

[Zeev Suraski]

As it should...  This bug should be closed.

At 20:25 10/2/2001, [EMAIL PROTECTED] wrote:
>ID: 1531
>Updated by: jimw
>Reported By: [EMAIL PROTECTED]
>Status: Open
>Old-Bug Type: Feature/Change Request
>Bug Type: Scripting Engine problem
>Assigned To:
>Comments:
>
>4.0 still gives the same message.
>
>Previous Comments:
>---
>
>[2000-08-17 11:48:09] [EMAIL PROTECTED]
>BD>> still it should not result in a parse error
>
> > It's not parse error, please read the message.
> > It didn't failed opening, it failed reading.
> > And require is not allowed to fail.
> > That's not unknown file, that's known non-file.
> >--
> >Stanislav Malyshev   [EMAIL PROTECTED]
>
>ok, got it now, i thought it was related to just ./,
>not directories in general
>
>but it fails for include to, while including for
>example a non-existing file produces the message
>i cited above and the error message is very
>misleading
>
>so i move this on to feature requests:
>
>1) should give clearer error-message
>
>2) at least include should treat directories
>like nonexistant (or empty?) files
>and issue a warning instead of a fatal error
>
>
>
>---
>
>[2000-08-17 11:21:40] [EMAIL PROTECTED]
>still it should not result in a parse error
>
>it should produce a warning
>
>   PHP Warning:  Failed opening './' for inclusion
>
>as with other unknown files
>
>---
>
>[2000-08-17 11:07:48] [EMAIL PROTECTED]
>I don't see problem here. ./ is not a file, and reading it as a file 
>fails. So it should be.
>
>---
>
>[2000-08-17 10:57:52] [EMAIL PROTECTED]
>still there even in 4.0.1
>
>---
>
>[1999-06-20 21:06:01] [EMAIL PROTECTED]
>Zeev knows about this one, and I believe it will
>be fixed in PHP4. There may actually be a very
>old bug on this as well.
>
>---
>
>The remainder of the comments for this report are too long.  To view the 
>rest of the comments, please view the bug report online.
>
>
>ATTENTION! Do NOT reply to this email!
>To reply, use the web interface found at http://bugs.php.net/?id=1531&edit=2
>
>
>--
>PHP Development Mailing List 
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>To contact the list administrators, e-mail: [EMAIL PROTECTED]

--
Zeev Suraski <[EMAIL PROTECTED]>
CTO &  co-founder, Zend Technologies Ltd. http://www.zend.com/


-- 
PHP Development Mailing List 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]