in reply to eval with semicolon

Because it's a simple statement like any other, not a special compiler directive compound statement that introduces a block. You need to put a semicolon after it whenever you'd need to put a semicolon after any simple statement. See perlsyn:

Simple Statements The only kind of simple statement is an expression evaluated for its side effects. Every simple statement must be terminated with a semicolon, unless it is the final statement in a block, in which cas +e the semicolon is optional. (A semicolon is still encouraged if the b +lock takes up more than one line, because you may eventually add another line.) Note that there are some operators like "eval {}" and "do {}" that look like compound statements, but aren't (they're just TERMs i +n an expression), and thus need an explicit termination if used as the la +st item in a statement.

Update: Fixed up terminology as per replies, below

-xdg

Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

Replies are listed 'Best First'.
Re^2: eval with semicolon
by pg (Canon) on Oct 02, 2005 at 17:52 UTC
    "not a special compiler directive"

    "preprocessing directive", or as you said "compiler directive", has its own specific meaning, and things like if, for, while etc. are not preprocessing directives. They are really flow control statement.

    They can often be further classified:

    • selection: for example, if;
    • iteration: for example, for;
    • loop control: for example, last;
    • jumping: for example: goto.

      Good point. Sloppy terminology on my part -- I hadn't meant pre-processing. From perlsyn, a "compound statement that introduces a block" is a better description of what eval is not.

      -xdg

      Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.