[#4595] New block syntax — Daniel Amelang <daniel.amelang@...>

I'm really sorry if this isn't the place to talk about this. I've

25 messages 2005/03/21
[#4606] Re: New block syntax — "David A. Black" <dblack@...> 2005/03/21

Hi --

[#4629] Re: New block syntax — "Sean E. Russell" <ser@...> 2005/03/30

On Monday 21 March 2005 16:17, David A. Black wrote:

[#4648] about REXML::Encoding — speakillof <speakillof@...>

Hi.

15 messages 2005/03/31
[#4659] Re: about REXML::Encoding — "Sean E. Russell" <ser@...> 2005/04/04

On Thursday 31 March 2005 09:44, speakillof wrote:

[ ruby-Bugs-1688 ] [PATCH] Bugfixes to ripper HEAD - broken depend, and regexp_literal lacks options

From: noreply@...
Date: 2005-03-25 22:07:02 UTC
List: ruby-core #4621
Bugs item #1688, was opened at 2005-03-25 22:01
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1698&aid=1688&group_id=426

Category: Core
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Mitchell Charity (mcharity)
Assigned to: Nobody (None)
Summary: [PATCH] Bugfixes to ripper HEAD - broken depend, and regexp_literal lacks options

Initial Comment:
Two bugfixes to ripper, CVS HEAD.
Patch attached.

(1) Bug fix, ext/ripper/depend

Problem: ext/ripper/lib/ripper/core.rb is not being rebuilt.

Solution: Renamed the target from "rb" to the file name.
Created a new target "rb" for backwards compatibility.

(2) Bug fix, parse.y, and thus ext/ripper/ripper.y

Problem: In parse.y, ripper's regepx_literal dispatch is not given the
regexp options.

Solution: Added the options ($3) to the dispatch.

Before
  $ ruby -rripper -rpp -e 'pp Ripper.sexp("/pat/mi")'
  [:program,
   [:stmts_add,
    [:stmts_new],
    [:regexp_literal,
     [:xstring_add, [:xstring_new], [:@tstring_content, "pat", [1, 1]]]]]]
After
  $ ruby -rripper -rpp -e 'pp Ripper.sexp("/pat/mi")'
  [:program,
   [:stmts_add,
    [:stmts_new],
    [:regexp_literal,
     [:xstring_add, [:xstring_new], [:@tstring_content, "pat", [1, 1]]],
     [:@regexp_end, "/mi", [1, 4]]]]]


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=1698&aid=1688&group_id=426

In This Thread

Prev Next