include 'filename.php' vs. exit 'whatever'

[yawnmoth]

To quote from <http://php.net/function.include>,

"Because include() is a special language construct, parentheses are
not needed around its argument. Take care when comparing return
value."

exit is a language construct, also. To quote from <http://php.net/
function.exit>,

"this is a language construct"

So why does include 'whatever' work while exit 'whatever' doesn't? If
include doesn't require parenthesis because it's a language construct,
that implies that no language construct requires parenthesis, but...
if I don't use parenthesis with exit, I get a syntax error...

[ELINTPimp]

On May 26, 10:51 pm, yawnmoth <[e-mail]:

To quote from <http://php.net/function.include>,

"Because include() is a special language construct, parentheses are
not needed around its argument. Take care when comparing return
value."

exit is a language construct, also. To quote from <http://php.net/
function.exit>,

"this is a language construct"

So why does include 'whatever' work while exit 'whatever' doesn't? If
include doesn't require parenthesis because it's a language construct,
that implies that no language construct requires parenthesis, but...
if I don't use parenthesis with exit, I get a syntax error...

You CAN use exit without parenthesis, using parenthesis allow you to
return an error code value. Note, using exit without passing an error
code is like passing exit(0).

If you are getting syntax error, could you please post the error...

From php.net code block examples:

Example #2 exit() status example
<?php

//exit program normally
exit;
exit();
exit(0);

//exit with an error code
exit(1);
exit(0376); //octal

?>

[Jerry Stuckle]

yawnmoth wrote:

To quote from <http://php.net/function.include>,

"Because include() is a special language construct, parentheses are
not needed around its argument. Take care when comparing return
value."

exit is a language construct, also. To quote from <http://php.net/
function.exit>,

"this is a language construct"

So why does include 'whatever' work while exit 'whatever' doesn't? If
include doesn't require parenthesis because it's a language construct,
that implies that no language construct requires parenthesis, but...
if I don't use parenthesis with exit, I get a syntax error...

Because that's the way the language is designed. exit() requires
parens, include doesn't.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attglobal.net
==================

[Gordon]

On May 27, 3:51 am, yawnmoth <[e-mail]:

To quote from <http://php.net/function.include>,

"Because include() is a special language construct, parentheses are
not needed around its argument. Take care when comparing return
value."

exit is a language construct, also. To quote from <http://php.net/
function.exit>,

"this is a language construct"

So why does include 'whatever' work while exit 'whatever' doesn't? If
include doesn't require parenthesis because it's a language construct,
that implies that no language construct requires parenthesis, but...
if I don't use parenthesis with exit, I get a syntax error...

The simple way around this problem is to just treat everything as if
it does require brackets. * always use brackets with return, die,
include etc and have never run into any problems.

[ELINTPimp]

On May 26, 11:05 pm, Jerry Stuckle <[e-mail]:

yawnmoth wrote:

To quote from <http://php.net/function.include>,

"Because include() is a special language construct, parentheses are
not needed around its argument. Take care when comparing return
value."

exit is a language construct, also. To quote from <http://php.net/
function.exit>,

"this is a language construct"

So why does include 'whatever' work while exit 'whatever' doesn't? If
include doesn't require parenthesis because it's a language construct,
that implies that no language construct requires parenthesis, but...
if I don't use parenthesis with exit, I get a syntax error...

Because that's the way the language is designed. exit() requires
parens, include doesn't.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
[e-mail]
==================

Anyone else not get a syntax error on use of exit; (without braces)
PHP 5.2.3, no reported syntax error with E_ALL turned on.

[Robin]

ELINTPimp wrote:

On May 26, 10:51 pm, yawnmoth <[e-mail]:

>To quote from <http://php.net/function.include>,

"Because include() is a special language construct, parentheses are
not needed around its argument. Take care when comparing return
value."

exit is a language construct, also. To quote from <http://php.net/
function.exit>,

"this is a language construct"

So why does include 'whatever' work while exit 'whatever' doesn't? If
include doesn't require parenthesis because it's a language construct,
that implies that no language construct requires parenthesis, but...
if I don't use parenthesis with exit, I get a syntax error...

You CAN use exit without parenthesis, using parenthesis allow you to
return an error code value. Note, using exit without passing an error
code is like passing exit(0).

If you are getting syntax error, could you please post the error...

From php.net code block examples:

Example #2 exit() status example
<?php

//exit program normally
exit;
exit();
exit(0);

//exit with an error code
exit(1);
exit(0376); //octal

?>

I think what the op is saying is:

if both these are valid:
include 'test.php';
include('test.php');

then why aren't both these:
exit 1;
exit(1);

The former exit giving the parse error.

I just use parenthesis everywhere to avoid the issue.

Robin

[ELINTPimp]

On May 27, 7:44 am, Robin <[e-mail]:

ELINTPimp wrote:

On May 26, 10:51 pm, yawnmoth <[e-mail]:

To quote from <http://php.net/function.include>,

"Because include() is a special language construct, parentheses are
not needed around its argument. Take care when comparing return
value."

exit is a language construct, also. To quote from <http://php.net/
function.exit>,

"this is a language construct"

So why does include 'whatever' work while exit 'whatever' doesn't? If
include doesn't require parenthesis because it's a language construct,
that implies that no language construct requires parenthesis, but...
if I don't use parenthesis with exit, I get a syntax error...

You CAN use exit without parenthesis, using parenthesis allow you to
return an error code value. Note, using exit without passing an error
code is like passing exit(0).

If you are getting syntax error, could you please post the error...

From php.net code block examples:

Example #2 exit() status example
<?php

//exit program normally
exit;
exit();
exit(0);

//exit with an error code
exit(1);
exit(0376); //octal

?>

I think what the op is saying is:

if both these are valid:
include 'test.php';
include('test.php');

then why aren't both these:
exit 1;
exit(1);

The former exit giving the parse error.

I just use parenthesis everywhere to avoid the issue.

Robin

Ah, now I'm on the same page.

[Jerry Stuckle]

ELINTPimp wrote:

On May 26, 11:05 pm, Jerry Stuckle <[e-mail]:

>yawnmoth wrote:

>>To quote from <http://php.net/function.include>,
"Because include() is a special language construct, parentheses are
not needed around its argument. Take care when comparing return
value."
exit is a language construct, also. To quote from <http://php.net/
function.exit>,
"this is a language construct"
So why does include 'whatever' work while exit 'whatever' doesn't? If
include doesn't require parenthesis because it's a language construct,
that implies that no language construct requires parenthesis, but...
if I don't use parenthesis with exit, I get a syntax error...

Because that's the way the language is designed. exit() requires
parens, include doesn't.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
[e-mail]
==================

Anyone else not get a syntax error on use of exit; (without braces)
PHP 5.2.3, no reported syntax error with E_ALL turned on.

With just exit; no. But try to pass a return value, i.e. exit 4;

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attglobal.net
==================

[Charles Calvert]

On Mon, 26 May 2008 23:05:11 -0400, Jerry Stuckle
<js*******@attglobal.netwrote in
<-p******************************@comcast.com>:

>yawnmoth wrote:

>To quote from <http://php.net/function.include>,

"Because include() is a special language construct, parentheses are
not needed around its argument. Take care when comparing return
value."

exit is a language construct, also. To quote from <http://php.net/
function.exit>,

"this is a language construct"

So why does include 'whatever' work while exit 'whatever' doesn't? If
include doesn't require parenthesis because it's a language construct,
that implies that no language construct requires parenthesis, but...
if I don't use parenthesis with exit, I get a syntax error...

Because that's the way the language is designed. exit() requires
parens, include doesn't.

And yes, it is inconsistent.
--
Charles Calvert | Software Design/Development
Celtic Wolf, Inc. | Project Management
http://www.celticwolf.com/ | Technical Writing
[phone] | Research

[Jerry Stuckle]

Charles Calvert wrote:

On Mon, 26 May 2008 23:05:11 -0400, Jerry Stuckle
<js*******@attglobal.netwrote in
<-p******************************@comcast.com>:

>yawnmoth wrote:

>>To quote from <http://php.net/function.include>,

"Because include() is a special language construct, parentheses are
not needed around its argument. Take care when comparing return
value."

exit is a language construct, also. To quote from <http://php.net/
function.exit>,

"this is a language construct"

So why does include 'whatever' work while exit 'whatever' doesn't? If
include doesn't require parenthesis because it's a language construct,
that implies that no language construct requires parenthesis, but...
if I don't use parenthesis with exit, I get a syntax error...

Because that's the way the language is designed. exit() requires
parens, include doesn't.

And yes, it is inconsistent.

I'm not arguing whether it is inconsistent or not - but that's the way
it works.

I suspect it goes back to C/C++, where exit() is a function call, but
#include is a preprocessor direction. Of course, since PHP doesn't have
a preprocessor, it just uses include.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attglobal.net
==================

[lawrence k]

On May 26, 10:51 pm, yawnmoth <[e-mail]:

So why does include 'whatever' work while exit 'whatever' doesn't? If
include doesn't require parenthesis because it's a language construct,
that implies that no language construct requires parenthesis, but...
if I don't use parenthesis with exit, I get a syntax error...

As Jerry Stuckle said, that is the way the language is designed. You
are drawing the wrong conclusion about what the phrase "langauge
construct" means. "language contructs" in PHP don't have to be
consistent with each other. PHP is notorious for its inconsistencies
(function names like str_replace and strpos remain embarrassments for
the language). When the documentation says "this is a language
construct" what they mean "this works in a wholly arbitrary manner,
defined here in the documentation".

[sheldonlg]

lawrence k wrote:

On May 26, 10:51 pm, yawnmoth <[e-mail]:

>So why does include 'whatever' work while exit 'whatever' doesn't? If
include doesn't require parenthesis because it's a language construct,
that implies that no language construct requires parenthesis, but...
if I don't use parenthesis with exit, I get a syntax error...

As Jerry Stuckle said, that is the way the language is designed. You
are drawing the wrong conclusion about what the phrase "langauge
construct" means. "language contructs" in PHP don't have to be
consistent with each other. PHP is notorious for its inconsistencies
(function names like str_replace and strpos remain embarrassments for
the language). When the documentation says "this is a language
construct" what they mean "this works in a wholly arbitrary manner,
defined here in the documentation".

Why do you say "str_replace and strpos remain embarrassments for
the language"? I just had occasion to use str_replace yesterday and it
did exactly the job I wanted.