Google Groups Home
Help | Sign in
'compiled' ruby
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  1 message - Collapse all
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
dave.dolan  
View profile
 More options Jun 12, 8:20 am
From: "dave.dolan" <dave.do...@gmail.com>
Date: Thu, 12 Jun 2008 05:20:17 -0700 (PDT)
Local: Thurs, Jun 12 2008 8:20 am
Subject: 'compiled' ruby
I was reading the list back a few weeks here I noticed that someone is
making the distinction between 'compiled' ruby (Ruby.net) vs
interpreted ruby (IronRuby).  What I would like to know is how are you
planning on dealing with the semantics of compiling ruby... like open
classes, method_missing, tricks like the interface switching library,
etc... the things that require actually rewriting the objects at
runtime.  I'm guessing someone already has a solution worked out for
it, but is there somewhere you can point me to read up on this better
for myself?  I think that many of the benefits of ruby are because it
is not compiled, and I was just trying to see if someone might speak
to that point.  This is purely an academic question here, I'm not
asking anyone for any particular action, I'm just very curious.

    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2008 Google