Is any one of them more "correct" than the other?

Relatedly, is it more common to have a space between "for" and the open bracket "("?

Update: For comparison, here's the (default) output from Perl::Tidy:

print 1 .. 10;
for ( 1 .. 10 ) { print; }
print for ( 1 .. 10 );
[download]

for my $number ( 1 .. 10 ) {
    print $number;
}
[download]

for my $number ( 1 .. 10 ) {
    $number *= $number;
    print $number, "\n";
}
[download]

This would allow you/someone else to more easily add more steps to the loop

The "easy to add another line" thing is a bit of a red herring; any decent editor can convert a postfix for to a block for with a single keypress.

The real reason to prefer block for is that it allows you to bind the loop variable to something other than $_ (eg your $number), which often makes for more readable code.

In bigger scripts or to write one-liner? I used syntax print for 1..10 (no parens at all - this syntax IMHO is designed to economize on parens, too), for short lines, but in bigger projects lines became longer and soon I had to break those lines somehow and to decide which line is short and which one long. And decided to go back to 'normal' syntax in every case.

for(1..10)
    { print; }
[download]

if there is only one line of code inside loop/if. No space after 'for' but space after '{' and before '}'.

And if second line of code must be added inside block or in 'for' there is more code, I always change to 'normal' mode:

for(1..10)
{
    print;
    $cnt++;
}
[download]

for(1..10,
    12..30,
    74..112)
{
    print
}
[download]

About your examble: It's a litte confusion what you like to show. In this special, actuall quite special, case print @array; is the common because it calls print only once.

Perl is about having multiple ways to do one thing, so your 2nd and 3rd line differ only in style, not in correctness. Note that the style in the 3rd line would also work for multiple commands while the 2nd line wouldn't.

If you generalise this example to the case that you like to call one function several times with each element of a list/array, then I would code it like this:

function($_) foreach (<list>);
# or
[download]

function($good_name) foreach my $good_name (<list>);
[download]

Also note that AFIK for and foreach do the same with the same arguments, you just should "use for when you mean for and use foreach when you mean foreach".

I hope you don't, cause

function($good_name) foreach my $good_name (<list>);
[download]

and specifically

$good_name(<list>)
[download]

are not valid Perl.

Thanks for pointing this out. I of course meant the following code:
foreach my $good_name (1..10) { function($good_name) }
in reverse style. I was just assuming that it's valid Perl. I only used the reverse style with if or while statements so far. For a reason my for/foreach loops are always bigger.

C:\>perl -le"print for 1..10
1
2
3
4
5
6
7
8
9
10

C:\>
[download]