If you want to embed newlines in your output (or any string) you shouldn't be doing it like this,

my $a;
$a = " Some stuff here
       Some more stuff on the next line ";
[download]

Although this works in some cases, you could concievably run into trouble when you take a script with such embedded newlines from a *nix type OS to a M$ operating system.

The other problem with embedding invisible newlines in quoted strings is that it is difficult to tell the difference between wrapped text and text with newlines. And it is difficult to find the end of the string. People just don't expect " quoted " text to span multiple lines. At very least, use the visible version of newline, "\n".

A more efficient and foolproof way of doing it if you have multiple lines of literal text is to use here documents. Here documents can be used directly within a print statement, or in an assignment statement, or anywhere else that a string is expected. Here's an example:

my $string = <<END_HERE;
Here is some text.
Newlines, though invisible, are
implicitly understood, and in fact,
are expected.  A here document won't
confuse people.
END_HERE
[download]

As I mentioned before, here documents can also be used directly within a print statement:

print << END_HERE;
Here is multi-line
text created with a 
here document.
END_HERE
[download]

An interesting thing about here documents is that the text is assumed to be "double quoted" unless you wrap the leading marker in some other type of quotes. And as we all know, double-quoted text is subject to variable interpolation as well as "\n" conversion. So each of the following examples use a different sort of quoting:

my $string;
$string = <<END_HERE;  # Seen as double quotes.
text
END_HERE

$string = <<"END_HERE"; # Same thing.

$string = <<'END_HERE'; # Interpolated as 'single quotes'.

$string = <<`END_HERE`; # Interpolated as `backtick` quoted text.

or even.....

( $string <<END_HERE ) =~ s/^\s+//gm;
   indented
   text becomes
   unindented
   because the substitution
   regexp removes
   preceding whitespace.
END_HERE

...and so on.
[download]

I dove into this response because I was concerned when I saw in the Q&A section the promotion of using multiline "quoted" text with embedded invisible newlines. Yes, it can work. Yes, it can be quite confusing. Yes, that's what here-docs are for.