I would agree with what you say except that I know
there's an incorrect and harmful prevailing attitude
out there that
"scripting" languages are in some way inferior, because
they don't create "real" programs. Honestly, I don't
think we'll get the C/C++ people to stop looking
crosseyed at us until we have an optimizing compiler
that produces platform-specific native binaries, and
I don't think a bundlemonkey approach (binding the
interpreter and the bytecode together into an
executable package) will do the trick. It's stupid,
something that's only needed because of misconceptions
that people have, but I'm pretty sure it's necessary,
politically, for at least one major VHLL to have this
before we'll be able to finally do away with the whole
issue.
;$;=sub{$/};@;=map{my($a,$b)=($_,$;);$;=sub{$a.$b->()}}
split//,".rekcah lreP rehtona tsuJ";$\=$;[-1]->();print
-
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.
|