Basically, Perl has its own way to interprete the syntax, for example to distinct the same operators or functions usage, based on some contexts. Parsing things such as $scalar->[0] or $scalar->{key}, or even $scalar->method is straightforward and will Do What I (programmer) Mean. Please see perlref for detail.
wont it get confused.Wont there be any ambiguity?
In case of ambiguity, Perl will try its best to Do What I (programmer) Really Mean. If it gets confused though, it may warn me, or I can make it confess to show more detail what or where it gets confused. This helps me to see that my code might not steadily represent what I mean. And if it really doesn't have any idea on some piece of code, or refuses to look further, it will die and let me informed that what and where in my code some part just doesn't make sense to it.
Open source softwares? Share and enjoy. Make profit from them if you can. Yet, share and enjoy!
-
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.
|
