[#1263] Draft of the updated Ruby FAQ — Dave Thomas <Dave@...>

33 messages 2000/02/08

[#1376] Re: Scripting versus programming — Andrew Hunt <andy@...>

Conrad writes:

13 messages 2000/02/15

[#1508] Ruby/GTK and the mainloop — Ian Main <imain@...>

17 messages 2000/02/19
[#1544] Re: Ruby/GTK and the mainloop — Yasushi Shoji <yashi@...> 2000/02/23

Hello Ian,

[#1550] Re: Ruby/GTK and the mainloop — Ian Main <imain@...> 2000/02/23

On Wed, Feb 23, 2000 at 02:56:10AM -0500, Yasushi Shoji wrote:

[#1516] Ruby: PLEASE use comp.lang.misc for all Ruby programming/technical questions/discussions!!!! — "Conrad Schneiker" <schneiker@...>

((FYI: This was sent to the Ruby mail list.))

10 messages 2000/02/19

[#1569] Re: Ruby: constructors, new and initialise — Yukihiro Matsumoto <matz@...>

The following message is a courtesy copy of an article

12 messages 2000/02/25

[ruby-talk:01563] Ruby supported/distributed libraries--can all be used together?

From: "Conrad Schneiker" <schneiker@...>
Date: 2000-02-24 10:16:56 UTC
List: ruby-talk #1563
(Found on comp.lang.misc.)

What problems would presently (or indefinitely) exist for doing the
following?

Let's say you have a really grandiose Ruby application that tries to
function as a general purpose assistant with respect to all the things that
the modules in the supported Ruby distribution can do. Let's say you have a
very fast file system and many 100s of megabytes of RAM. For purposes of
minimizing startup time, could _all_ the modules first be imported, then
initialized, and finally, could the process execution image at that point be
saved for subsequent restarting, at which point the main program would
proceed? Are there problems with dynamic linking of Ruby extensions and such
that would thwart any substantial time savings? Are there any modules that
set global variables in incompatible ways upon initialization?

In the event that there are no insuperable showstoppers at this point, is
there anything that would preclude you from eventually including all modules
from the future greater Ruby archive? If so, is there some half way
reasonable criteria for writing modules that would make this feasible?

Conrad



In This Thread

Prev Next