And while we are in the maybes
- Maybe Ruby will get a little bit more clever in letting me spread a statement over several lines without jumping through hooooooops that much.
x = 1 + 2
+ 3
puts x
prints 3. That's kinda what I'd expect from a language that more or less uses the newline character as the statement terminator. But even
x = (1 + 2
+ 3)
prints 3. (Sorry? How???)
x = foo(1 + 2
+ 3)
on the other hand errors out with "syntax error, unexpected tUPLUS, expecting ')'". Lovely. Choose between
the two ugly options
x = foo(1 + 2 +
3)
and
x = foo(1 + 2 \
+ 3)
- Maybe sometime in the future it will get sensible error messages. "unexpected tUPLUS"? What the f..k? And that's one of the least cryptic I've seen.
- Maybe in a few years the Ruby folk gets through the discussion that was hot in the Perl community some eight years ago and add variable declaration and use strict. (There is currently no way to know whether an "x" used in a block is a new local one or shared with a bigger scope. And no way to specify that. And to make things more interesting the locality of the block parameters is currently context dependent, in the upcomming version they will always be local. Sweet.) Currently all you get is a runtime check that the first thing you do to a variable is some kind of assignment.
-
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.
|