$ perl -c -e " use strict; use warnings; BEGIN { $sumeet = 1; } $grove
+r = 1; } "
Global symbol "$sumeet" requires explicit package name at -e line 1.
BEGIN not safe after errors--compilation aborted at -e line 1.

$ perl -c -e " use strict; use warnings; BEGIN { our $sumeet = 1; } $g
+rover = 1; } "
Global symbol "$grover" 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.

$ perl -c -e " use strict; use warnings; BEGIN { our $sumeet = 1; } $g
+rover = 1; "
Global symbol "$grover" requires explicit package name at -e line 1.
-e had compilation errors.

$ perl -c -e " use strict; use warnings; BEGIN { our $sumeet = 1; } ou
+r $grover = 1; "
-e syntax OK
[download]

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]

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.

On no semicolons, see also Programming in Perl without semicolon.