From: "Haase, Konstantin" <Konstantin.Haase@...>
Date: 2010-12-14T19:04:21+09:00
Subject: [ruby-core:33715] Re: Towards a standardized AST for Ruby code

On Dec 14, 2010, at 10:11 , Charles Oliver Nutter wrote:

> On Tue, Dec 14, 2010 at 3:05 AM, Haase, Konstantin
> <Konstantin.Haase@student.hpi.uni-potsdam.de> wrote:
>> Being able toe turn it on and off during runtime would be a great feature and would reduce memory overhead.
> 
> If you haven't loaded code with the source saved, you can't really get
> it back. On and off at runtime would only make sense for code
> yet-to-be-parsed.

Yeah, but that's what I'm getting at. Say, I load the system, maybe even gems I need and don't care for their code. Then I activate the source tracking, load my app code, parse the AST with RubyParser, do some transformations, disable the source tracking again, redefine some methods and run the app. Doing it as a flag that will affect the complete life cycle of my app will have such a performance/memory impact that say partial evaluation wouldn't be feasible.

Konstantin