Re^2: Non-traditional, Line by Line Compilation in Perl

Replies are listed 'Best First'.
Re^3: Non-traditional, Line by Line Compilation in Perl by Anonymous Monk on Dec 07, 2011 at 12:01 UTC
Agreed, compilation would be based on statements, separated by semicolon! We don't need no stinkin semicolons !:) `$ perl -c -e " use strict; use warnings; { $foo = 1 } { $bar }} " Global symbol "$foo" requires explicit package name at -e line 1. Global symbol "$bar" requires explicit package name at -e line 1. Unmatched right curly bracket at -e line 1, at end of line syntax error at -e line 1, near "}}" -e had compilation errors.` [download] `$ perl -e " use strict; use warnings; { our $foo = 1 } { our $bar } p +rint 666" 666` [download]	[reply] [d/l] [select]
Re^4: Non-traditional, Line by Line Compilation in Perl by sumeetgrover (Monk) on Dec 07, 2011 at 12:24 UTC
Well, I certainly do prefer using semicolons, having first learned C programming. I also regard using semi colons at the end of programming statements to be a good programming / software-development practice.	[reply]
Re^4: Non-traditional, Line by Line Compilation in Perl by ambrus (Abbot) on Dec 10, 2011 at 21:06 UTC
On no semicolons, see also Programming in Perl without semicolon.	[reply]