It's not just the syntax that gets in the way with JavaScript -- it's the broken implementations and the short-sighted language definition (no direct system I/O, for example). It's a good language the same way Lance Armstrong would be a good athlete if he was was riding a circa 1980 banana seat bicycle designed for a ten year old girl in the Tour de France.
Anyhow -- yeah, I agree, regarding "anything that helps writing real functional code", as long as it doesn't also get in the way of writing real useful code. I'm not saying that writing real functional code necessarily makes the code less useful -- just that I've seen some people do some really boneheaded things with language design for the purpose of rigidly adhering to some kind of design aesthetic.
Thanks for the link about implementing amb in Perl, and the other commentary. I'll need to get significantly more well versed in things Lispy to really appreciate macros, I think, but one of the things I tend to look for in a programming language is duck typing or, alternatively, type inference. Thus, none of your suggestions really go amiss for me.
print substr("Just another Perl hacker", 0, -2); |
|
- apotheon
CopyWrite Chad Perrin |
-
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.
|