OK. It's done and nothing broke.
On Jul 9, 2007, at 1:46 PM, Charles Oliver Nutter wrote:
Alan McKean wrote:
OK. Let me make sure I understand ... these are all static in
class Ruby. Then I call setCurrentInstance() in newInstance
(RubyConfig), and I always use getCurrentInstance() in my la
Alan McKean wrote:
OK. Let me make sure I understand ... these are all static in class
Ruby. Then I call setCurrentInstance() in newInstance(RubyConfig), and I
always use getCurrentInstance() in my lazy initializers: getMarshal(),
getMethods(), etc. Correct?
That's the idea. The only depende
OK. Let me make sure I understand ... these are all static in class
Ruby. Then I call setCurrentInstance() in newInstance(RubyConfig),
and I always use getCurrentInstance() in my lazy initializers:
getMarshal(), getMethods(), etc. Correct?
On Jul 9, 2007, at 9:12 AM, Charles Oliver Nutter
On 7/8/07, Charles Oliver Nutter <[EMAIL PROTECTED]> wrote:
dreamhead wrote:
> Hi!
>
> JRuby has a wonderful idea about method which is to generate method
> class. We all know that it takes some time to do that, so it's good
> idea to save the result.
>
> In JRuby, DumpingInvocationCallbackFactor
Alan McKean wrote:
So far, everything seems to work. But I have some questsions about the
runtime. When Rails is running multiple runtimes, does it maintain a
pool of them or does it instantiate a new runtime every time it needs
one. I currently have only one runtime. It's a singleton and I use
Yes. The single runtime is stored in a static Ruby 'instance'
On Jul 8, 2007, at 2:39 AM, Ola Bini wrote:
Alan McKean wrote:
So far, everything seems to work. But I have some questsions about
the runtime. When Rails is running multiple runtimes, does it
maintain a pool of them or does it
