Difference in include behaviour in --1.9 mode

Still valid in 1.6.3

Very basic problem with constant resolution in top-level scope. Embarrasing Marking for 1.7

On master, this fails the same in both 1.8 and 1.9 mode, compiled or interpreted. Something basic about toplevel include + const lookup is failing us here.

Investigating.

Interestingly, accessing just "Generator" works fine. So it seems to be something wrong with how colon2 (Generator::Literal) is working.

LOL.

So the actual problem here is that we define a top-level Generator class to support Enumerator#next, regardless of whether generator.rb has been required. We're not incorrectly failing to find the Literal constant...we're correctly finding our Generator instead of yours.

If I require 'generator' in Ruby 1.8, it fails exactly the same way. That library does not exist in 1.9.

I guess this is a good time to consider namespacing our always-present Generator class out of toplevel.

Forgot to resolve this.

commit 05aa55457433554900e7d3369796cd5e5f2d0db8
Author: Charles Oliver Nutter <headius@headius.com>
Date:   Fri Sep 7 15:22:45 2012 -0500

    Fix JRUBY-5674: Difference in include behaviour in --1.9 mode
    
    The problem was not actually a difference in include behavior;
    the issue was that we were always defining a top-level Generator
    class that interfered with the lookup of the user's library's
    Generator class. Moved Generator to JRuby::Generator to avoid the
    namespace pollution.

:000000 100644 0000000... ad5ac9c... A	src/jruby/kernel/jruby/generator.rb