Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Aug 31, 2012
  1. Add spec for require after $LOAD_PATH change

    When developer add something to $LOAD_PATH and require once again the
    same file ruby should not require it once again.
    Rubinius have lib/racc/parser.rb file. And this file will require after
      require 'racc/parser'
    After require 'rubygems' $LOAD_PATH will change and now we have access
    to two version on 'racc/parser' (from Rubinius /lib and /gems/racc).
    When user try to require once again rubinius will search via $LOAD_PATH
    and hit racc/parser from _RUBYGEMS_. In ruby 1.9 mode all paths are
    expanded so rubinius will require once again 'racc/parser'. This is
    because in $LOADED_FEATURES we can find only
    "[rubinius_path]/lib/racc/parser.rb". When CodeLoader will find file in
    $LOAD_PATH ([rubygems]/racc/parser.rb) and full path is not part of
    $LOADED_FEATURES this file will be load once again.
Commits on Aug 30, 2012
  1. @brixen
  2. @brixen

    Renamed VMMethod to MachineCode.

    brixen authored
    This was a difficult name choice but it is consistent with CompiledCode
    and (not yet used) SourceCode. The CompiledCode is an abstraction of
    computation that is the focal point around which much revolves. MachineCode
    is a representation of computation specialized for our (virtual) machine.
    While there is possible ambiguity against the idea of JIT'd machine code,
    our MachineCode is a proper data structure, not just the format of bits
    resulting from the JIT compilation process. Also, our MachineCode is properly
    scoped differently than any such class/concept in LLVM (or more generally,
    the JIT).
    Regarding naming of instances of MachineCode, the following rationale is used:
    * parameters/variables have been named 'mcode' since the use of the variable
      is elaborated by the surrounding code (ie making ambiguity less an issue)
      and long variable names can sometimes make code unweildy.
    * attributes/fields/accessors have been name 'machine_code' because they have
      less context to disambiguate.
  3. @dbussink

    Implement rb_iter_break()

    dbussink authored
  4. @dbussink

    Add specs for rb_iter_break

    dbussink authored
Commits on Aug 29, 2012
  1. @dbussink
  2. @dbussink
  3. @dbussink

    Add specs for rb_catch

    dbussink authored
  4. @dbussink
Commits on Aug 27, 2012
  1. @brixen

    Merge pull request #1879 from r-stu31/configure_flags

    brixen authored
    configure: add CPPFLAGS and LDFLAGS where missing
  2. @brixen
  3. @r-stu31
  4. @r-stu31

    Use CPPFLAGS and LDFLAGS when checking libraries, after all, they are…

    r-stu31 authored
    … also used afterwards for the real compilation and linking.
  5. @dbussink

    Merge pull request #1875 from LTe/random_range

    dbussink authored
    Random with range
Commits on Aug 26, 2012
  1. @strcmp

    Merge pull request #1878 from robgleeson/59b878bb9a1acdab0055a83887c1…

    strcmp authored
    Expand "~" from File.absolute_path properly.
  2. @strcmp
  3. @strcmp

    Add failing spec for #1877.

    strcmp authored
  4. @strcmp
  5. @dbussink
  6. @dbussink

    Add specs for sorting shifted arrays

    dbussink authored
    This verifies that sorting still works if implementations use internal
    offsets for arrays.
  7. @dbussink
  8. @dbussink
  9. @dbussink
Commits on Aug 25, 2012
  1. @brixen
Commits on Aug 24, 2012
  1. @brixen
  2. @brixen
  3. @brixen
  4. @brixen
  5. @brixen
  6. @brixen
Commits on Aug 23, 2012
  1. @IPGlider

    Add tag for failing spec

    IPGlider authored
  2. @IPGlider

    Duplicate the spec for diferent ruby versions

    IPGlider authored
    This spec returns 4 on MRI 1.8.7p358 and 2 on MRI 1.9.3p194.
Commits on Aug 22, 2012
  1. @dbussink

    Flags can be passed in as nil

    dbussink authored
    Fixes #1611
Something went wrong with that request. Please try again.