[#24105] [Bug #1711] Marshal Failing to Round-Trip Certain Recurisve Data Structures — Run Paint Run Run <redmine@...>

Bug #1711: Marshal Failing to Round-Trip Certain Recurisve Data Structures

9 messages 2009/07/01

[#24116] [Bug #1715] Numeric#arg for NaN is Inconsistent Across Versions — Run Paint Run Run <redmine@...>

Bug #1715: Numeric#arg for NaN is Inconsistent Across Versions

10 messages 2009/07/02

[#24240] [Bug #1755] IO#reopen Doesn't Fully Associate with Given Stream on 1.9; Ignores pos on 1.8 — Run Paint Run Run <redmine@...>

Bug #1755: IO#reopen Doesn't Fully Associate with Given Stream on 1.9; Ignores pos on 1.8

8 messages 2009/07/09

[#24321] [Bug #1773] Gem path doesn't honor user gem? — Lin Jen-Shin <redmine@...>

Bug #1773: Gem path doesn't honor user gem?

12 messages 2009/07/14

[#24390] [Feature #1784] More encoding (Big5 series) support? — Lin Jen-Shin <redmine@...>

Feature #1784: More encoding (Big5 series) support?

12 messages 2009/07/16

[#24467] Re: [ruby-cvs:31226] Ruby:r24008 (ruby_1_8_6): Removed private on to_date and to_datetime. — Urabe Shyouhei <shyouhei@...>

Hello.

10 messages 2009/07/21

[#24472] [Feature #1800] rubygems can replace system executable files — Kazuhiro NISHIYAMA <redmine@...>

Feature #1800: rubygems can replace system executable files

13 messages 2009/07/21

[#24530] [Feature #1811] Default BasicSocket.do_not_reverse_lookup to true — Roger Pack <redmine@...>

Feature #1811: Default BasicSocket.do_not_reverse_lookup to true

9 messages 2009/07/23

[#24624] [Bug #1844] Immediates Should Not Respond to :dup — Run Paint Run Run <redmine@...>

Bug #1844: Immediates Should Not Respond to :dup

15 messages 2009/07/30

[ruby-core:24311] [RCR] allow for cleaner multi-line comments

From: Roger Pack <rogerdpack@...>
Date: 2009-07-13 12:41:16 UTC
List: ruby-core #24311
Forgive the radicalness of this idea.

Background: currently if one wants to temporarily comment out more
than one ruby code line [and doesn't have an editor to do it for them,
and doesn't want to put the whole thing into a string].

The only possible ways are:

 def go a, b
  #some code
  # ...
  #more code
 end

or

 def go a, b
=begin
  some code
   ...
  more code
=end
 end

The first example is somewhat time consuming for large blocks (esp.
for thos of us with poor editors like myself).  The second example [to
me] is somewhat harsh on the eyes because it interrupts the code flow.

Suggestion: allow for multi-line comments more easily.

one option would be:
allow for /* */ blocks

another would be
allow =begin and =end to have preceding whitespace allowable.

Our example becomes:
 def go a, b
  =begin
  some code
   ...
  more code
  =end
 end

Either would help out at least this ruby user (though my personal
preference would be for the latter--probably would require tweaking
the parser less].
I'd be happy to attempt a patch for either way.
Thoughts?
r

In This Thread

Prev Next