Yes, that is fine. The problems come in when you want to strip some of the leading whitespace:
print unindent( <<" END" );
Usage: $0 [flags] [args]
Gropples the snarflog.
-v Verbose.
-t mode Mode of groppling to use. "mode" can be:
fast Minimize execution time.
hard Maximize decryption time.
wide Minimize alphabet size.
Do not use on UTF8 files.
END
Any attempt to write an unindent() for the above will run into problems in the face of 1) editors that insert tabs when maintenance work modifies the text, and 2) people who don't agree on how far apart tabstops should be set.
The only solution I've found that I like goes something like this:
sub unindent { s/^\s*\S//gm }
print unindent( <<" END" );
.Usage: $0 [flags] [args]
.Gropples the snarflog.
. -v Verbose.
. -t mode Mode of groppling to use. "mode" can be:
. fast Minimize execution time.
. hard Maximize decryption time.
. wide Minimize alphabet size.
.Do not use on UTF8 files.
END
-
tye
(but my friends call me "Tye")
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|