[#10853] Why limit class def to a constant or colon node? — Charles Oliver Nutter <charles.nutter@...>

Is there a historical reason why I can't do something like these:

12 messages 2007/04/03

[#10933] Cannot build with extra library path if previous version already installed — <noreply@...>

Bugs item #10140, was opened at 2007-04-16 17:32

10 messages 2007/04/16
[#10934] Re: [ ruby-Bugs-10140 ] Cannot build with extra library path if previous version already installed — nobu@... 2007/04/16

Hi,

[#10960] Re: [ ruby-Bugs-10140 ] Cannot build with extra library path if previous version already installed — "Michal Suchanek" <hramrach@...> 2007/04/18

On 4/16/07, nobu@ruby-lang.org <nobu@ruby-lang.org> wrote:

[#10967] Re: [ ruby-Bugs-10140 ] Cannot build with extra library path if previous version already installed — Nobuyoshi Nakada <nobu@...> 2007/04/19

Hi,

[#10970] Re: [ ruby-Bugs-10140 ] Cannot build with extra library path if previous version already installed — "Michal Suchanek" <hramrach@...> 2007/04/19

On 4/19/07, Nobuyoshi Nakada <nobu@ruby-lang.org> wrote:> Hi,>> At Wed, 18 Apr 2007 20:21:44 +0900,> Michal Suchanek wrote in [ruby-core:10960]:> > Yes. And this should also apply to extensions. The mkmf tests are now> > fine but the extension is linked with -L/sw/lib before -L../..>> Indeed.>>> Index: configure.in> ===================================================================> --- configure.in (revision 12191)> +++ configure.in (working copy)> @@ -1385,5 +1385,4 @@ if test "$enable_rpath" = yes; then> fi>> -LDFLAGS="-L. $LDFLAGS"> AC_SUBST(ARCHFILE)>This would break the previous fix so I did not even try to apply this ^

[#11003] miniruby loads extensions from already installed ruby — <noreply@...>

Bugs item #10303, was opened at 2007-04-23 10:44

10 messages 2007/04/23

[#11025] gsub with backslash characters in replacement string — "Adam Bozanich" <adam.boz@...>

Hello, spotted this one the other day:

10 messages 2007/04/26

Re: YARV bytecode compiler in Ruby?

From: Charles Oliver Nutter <charles.nutter@...>
Date: 2007-04-10 07:04:13 UTC
List: ruby-core #10904
Rick DeNatale wrote:
>  From what I've seen of the 1.9 code, there really isn't a compiler
> from Ruby to YARV bytecodes per-se.  It's still using the old compiler
> which generates an abstract syntax tree, then YARV generates the
> bytecode from the AST.

Yes, and perhaps that's one reason why there's no ruby-based compiler 
right now: no standard AST API in the main dists. Granted I'm not 
familiar enough with "ripper", knowing only the ParseTree libraries, 
both in C and JRuby, but it seems like it would be of tremendous value 
to have a ruby-based compiler for YARV bytescodes. As it stands now, we 
can choose to use Rubinius bytecodes, for which there's a 
ParseTree-based compiler, or YARV, for which we'd have to implement our 
own compiler (already started by Ola). One has the benefit of requiring 
much less effort to use and maintain, and one has the benefit of 
compatibility with "official" Ruby 2.0 work.

- Charlie

In This Thread

Prev Next