Why does
1 #!perl
2 # Utility vars
3
4 my $foo="Hello there"
5
6 # End utility vars. When do we make these go away?
7
8 ######################################################
9 # We loop over each character and print them out
10 # this is mostly so that we can do the fnorzle with
11 # boopat over the dulwhup. Which can really pjorn your
12 # noodle
13
14
15 for my $i (0.. length($foo)-1) {
16 print "$i ",substr($foo,$i,1),"\n";
17 }
produce the following error
syntax error at D:\perl\scratch\errors.pl line 15, near "$i ("
Execution of D:\perl\scratch\errors.pl aborted due to compilation erro
+rs.
I dont see why this doesn't produce something more intelligent. My general rule for perl errors is that if I don't see the problem immediately on the line that perl tells me I look on the one before, and as the contrived example shows here that can be quite a ways before.
:-)
---
demerphq
<Elian> And I do take a kind of perverse pleasure in having an OO assembly language...
-
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.
|