Thanks for your input guys.

I want to say that I do really like Ruby. I'm just probing to see if 
there's improvements that can still be made, or whether it's as good as 
it can be already.

Oh, and I do realize the ambiguity of my last example.

Here's my thoughts on that:

I think you should ALWAYS be able to retrieve the "context" of an object 
given an object reference.

In compiled, statically-typed languages such as C++ or Java.
objects can access their "class context" by using:
obj.class

They cannot access their "block context", by well they don't have to, 
because Java blocks aren't first-class objects like they are in Ruby.

I think, given an object, you should be able to access their 
"block"/"scope", because Ruby actually treats them as first-class 
objects.

So my example would look something like this:

block.scope.instance_eval do
  def myMethod
  end
end

Anyway, thanks for the discussion. It's nice to read a thoughtful 
response.
  -Patrick

PS: I am actually currently investigating Smalltalk. I like the syntax, 
and the system, but Ruby does have one big advantage over it. It's 
standardized.
I can't even find a book that discusses the Smalltalk in depth, because 
there's so many different versions.
-- 
Posted via http://www.ruby-forum.com/.