34577-35477

34385-36946 subjects 34809-37155

^ Importing rubygems 1.5.0 (release candidate) into trunk.
34577 [ryand-ruby z] I'm going to be committing rubygems 1.5.0 into trunk in a bit.
+ 34588 [naruse airem] rubygems v1.3.7
| + 34590 [headius head] Perhas JRuby's approach would work well here? JRuby maintains a forked
| | 34626 [ryand-ruby z] minor is the keyword there. 1700 lines of diff is not minor. at about =
| | 34687 [headius head] ish lines of diff, I think the version should be changed. What 1.9.2 has be=
| + 34624 [ryand-ruby z] There are no bugs so bad that we should throw process out the window.
+ 34599 [mame tsg.ne.] Great.
| 34627 [ryand-ruby z] version we've released.
+ 34609 [usa garbagec] At where?
  + 34613 [luislavena g] ) into trunk."
  | 34625 [ryand-ruby z] Yeah. JRuby had the same bug. I'm not sure why, but some platforms set =
  + 34623 [ryand-ruby z] candidate) into trunk."
    34635 [usa garbagec] Thank you for explaining.

^ [Backport87-Backport#4293][Open] Errno::ENOMEM writing to STDOUT. Regression in 1.8.7-p330
34579 [redmine ruby] Backport #4293: Errno::ENOMEM writing to STDOUT. Regression in 1.8.7-p330

^ [Ruby 1.9-Bug#4168] WeakRef is unsafe to use in Ruby 1.9
34587 [redmine ruby] Issue #4168 has been updated by Kurt  Stephens.

^ [Backport87-Backport#4293][Assigned] Errno::ENOMEM writing to STDOUT. Regression in 1.8.7-p330
34591 [redmine ruby] Issue #4293 has been updated by Shyouhei Urabe.

^ [Backport87-Backport#4293] Errno::ENOMEM writing to STDOUT. Regression in 1.8.7-p330
34592 [redmine ruby] Issue #4293 has been updated by Usaku NAKAMURA.

^ Autoload treatment of absolute paths in $LOAD_PATH containing . or ..
34593 [yipdw member] I've run into a behavior with autoload and $LOAD_PATH that is inconsistent
35475 [rogerdpack2 ] I think so. I'm thinking it's a bug, unless other disagree?
35477 [quixoticsyco] This is in the backport queue. http://redmine.ruby-lang.org/issues/4446

^ [Backport87-Backport#4293] Errno::ENOMEM writing to STDOUT. Regression in 1.8.7-p330
34597 [redmine ruby] Issue #4293 has been updated by Shyouhei Urabe.

^ [Ruby 1.9-Bug#4009] Segfault with combination of threads and condition variables
34605 [redmine ruby] Issue #4009 has been updated by Tomoyuki Chikanaga.

^ [Ruby 1.9-Bug#4168] WeakRef is unsafe to use in Ruby 1.9
34606 [redmine ruby] Issue #4168 has been updated by Kurt  Stephens.

^ [Ruby 1.9-Bug#4294][Open] IO.popen ['"ping"', 'localhost -n 3'] fails
34610 [redmine ruby] Bug #4294: IO.popen ['"ping"', 'localhost -n 3'] fails

^ [Ruby 1.9-Bug#4294] IO.popen ['"ping"', 'localhost -n 3'] fails
34611 [redmine ruby] Issue #4294 has been updated by Jonas Pfenniger.

^ [Ruby 1.9-Bug#4294] IO.popen ['"ping"', 'localhost -n 3'] fails
34612 [redmine ruby] Issue #4294 has been updated by Jon Forums.

^ Re: Avoiding $LOAD_PATH pollution
34614 [jonas pfenni] The attached patch implements my previous proposition but is not final.

^ [Ruby 1.9-Bug#3967] rdoc generates bad HTML output for '...' in parameter list, call-seq: with multiple values
34615 [redmine ruby] Issue #3967 has been updated by mathew murphy.

^ [Ruby 1.9-Bug#4168] WeakRef is unsafe to use in Ruby 1.9
34620 [redmine ruby] Issue #4168 has been updated by Charles Nutter.

^ [Ruby 1.9-Bug#4168] WeakRef is unsafe to use in Ruby 1.9
34622 [redmine ruby] Issue #4168 has been updated by Charles Nutter.

^ Ruby operator equivalent to Groovy's "?."
34632 [rr.rosas gma] This is a multi-part message in MIME format.
+ 34633 [rr.rosas gma] This is a multi-part message in MIME format.
+ 34639 [duerst it.ao] I have definitely had cases where such a feature would have been very
| 34647 [jonas pfenni] dy.
| 34651 [ghazel gmail] ndy.
| 34657 [jonas pfenni] Yes, #try is an implementation of that idea. But as I said, there is
+ 34646 [giuseppe.bil] I think there's plenty of interest in such a feature, as it seriously
| + 34661 [rr.rosas gma] Yes, I've thought on that '.?' syntax too, but I wasn't very comfortable
| | 34672 [rb janlelis.] You could also use the egonil <http://rubyzucker.info/#egonil> or andand
| | + 34681 [rr.rosas gma] Regarding AndAnd, I still prefer obj._?.some_method to
| | + 34727 [yugui yugui.] These libraries are cool.
| + 34671 [ruby-ml kitt] obj.foo.bar.baz rescue nil
|   34673 [rr.rosas gma] Yes, Ruby is not that bad dealing with this, but I would rather prefer
+ 34692 [headius head] I'm not opposed to the feature, but it does tend to cause nils to
  34693 [jim.weirich ] Also doesn't work if a method returns a type other than self.class.
  34698 [headius head] Well, you'd mix this into Object or something if you wanted it globally...
  + 34700 [jballanc gma] Really, this is a deeper question of programming philosophy. The problem
  | 34701 [jballanc gma] ... I guess I should also add, however, that this is not exactly equivalent
  + 34740 [jim.weirich ] Sorry, I was confused.  I was thinking the instance_eval was applied

^ Returning from the callee
34634 [rr.rosas gma] This is a multi-part message in MIME format.
+ 34640 [mame tsg.ne.] I thought it too.
| 34662 [rr.rosas gma] Yes, although Japanese seems like a bunch of scribbles to me, Google
+ 34652 [jonas pfenni] This is usually solved by using Kernel#throw and Kernel#catch
| 34670 [rr.rosas gma] The problem with that approach is that it can only be used by the
| + 34683 [now bitwi.se] unless request.valid?
| | 34684 [rr.rosas gma] What I really want is a simple way for doing simple things. I usually
| | + 34686 [judofyr gmai] This is actually possible using catch/throw, and I believe `render` in
| | | 34744 [rr.rosas gma] Indeed, I agree. Probably this is not a good use case where a "return
| | + 34704 [radek.bulat ] render text: 'failed' && return unless request.valid?
| |   34728 [rr.rosas gma] As I said, render return value is not specified in the API, nor it
| + 34730 [jonas pfenni] Yes it's possible, the contract has to be defined by the framework
|   34745 [rr.rosas gma] Yes, I agree for this specific use case, although I still think this
+ 34653 [now bitwi.se] lee
  34663 [rr.rosas gma] I was trying to be concise, but I guess it wasn't a good idea. Let me

^ [Ruby 1.8-Bug#4295][Open] Time.utc(1960) raises ArgumentError: argument out of range (on Windows)
34636 [redmine ruby] Bug #4295: Time.utc(1960) raises ArgumentError: argument out of range (on Windows)

^ [Ruby 1.8-Bug#4295][Rejected] Time.utc(1960) raises ArgumentError: argument out of range (on Windows)
34637 [redmine ruby] Issue #4295 has been updated by Usaku NAKAMURA.

^ [Ruby 1.9-Bug#4297][Assigned] test_time in ruby/test/psych/test_json_tree.rb makes test failure
34641 [redmine ruby] Bug #4297: test_time in ruby/test/psych/test_json_tree.rb makes test failure
34656 [eregontp gma] =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=

^ [Ruby 1.9-Bug#4294] IO.popen ['"ping"', 'localhost -n 3'] fails
34642 [redmine ruby] Issue #4294 has been updated by red stun.
34644 [usa garbagec] I agree that the difference between the string form and the array

^ [Ruby 1.8-Bug#4295] Time.utc(1960) raises ArgumentError: argument out of range (on Windows)
34643 [redmine ruby] Issue #4295 has been updated by Greg Hazel.

^ [Ruby 1.9-Bug#4256] [BUG] Segmentation fault ruby 1.9.2p0 (2010-08-18) [i386-mingw32]
34645 [redmine ruby] Issue #4256 has been updated by Rama Mahendravada.

^ [Ruby 1.9-Bug#4298][Open] Duration of calling String#[] with the same index is strangely related to string length.
34648 [redmine ruby] Bug #4298: Duration of calling String#[] with the same index is strangely=

^ [Ruby 1.9-Bug#4298] Duration of calling String#[] with the same index is strangely related to string length.
34649 [redmine ruby] Issue #4298 has been updated by Rados• £¬w Bu• £¬t.

^ [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
34650 [redmine ruby] Issue #4239 has been updated by Zeno Davatz.
+ 34655 [jonas pfenni] f the cases. When I try to run my Ruby 1.8 Apps on Ruby 1.9 all of them hav=
+ 34660 [matz ruby-la] Your wording is little bit different from us.  We call your
+ 34760 [meta pobox.c] The thing you seem to be missing is that *consistency should only go one way*.
+ 34789 [cezary.bagin] Dear Zeno,
  34790 [goyox86 gmai] CgpCZXJuYXJkIExhbWJlYXUgPGJsYW1iZWF1QGdtYWlsLmNvbT4gd3JvdGU6Cgo+RGVhciBaZW5v

^ MRI file architecture doc
34659 [jonas pfenni] I started documenting the role of the files in the MRI svn trunk. Can
+ 34682 [naruse airem] Ruby is portable; Ruby works on Linux, *BSD, Windows, Symbian, and so on.
| 34699 [kosaki.motoh] Hmm..
| + 34705 [naruse airem] ved
| + 34718 [eregontp gma] I agree, README.FILES is about the project structure and you should be
| + 34729 [rr.rosas gma] I think the Rails approach to documentation is fantastic and could be
+ 34694 [usa garbagec] Not only for VC++. mingw uses some files in this directory.

^ [Ruby 1.9-Bug#4009] Segfault with combination of threads and condition variables
34664 [redmine ruby] Issue #4009 has been updated by Tomoyuki Chikanaga.

^ [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
34665 [redmine ruby] Issue #4239 has been updated by Zeno Davatz.
+ 34666 [matz ruby-la] I have no experience on Micro-Kernel development, so that I cannot say
| 34676 [naruse airem] It is intended changeon r26687.
+ 34668 [cremes.devli] The 1.9.0 and 1.9.1 releases were test beds for the new syntax and behavior. Neither one was intended for production use. The 1.9.2 release is targeted for production use.
+ 34678 [naruse airem] Ah, I understand what you say.

^ [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
34667 [redmine ruby] Issue #4239 has been updated by Zeno Davatz.

^ [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
34669 [redmine ruby] Issue #4239 has been updated by Zeno Davatz.
34677 [matz ruby-la] I am not sure how much you know about the development cycle of Ruby,

^ [Ruby 1.8-Bug#4139] abort and core dump in ruby 1.8.7-p302
34674 [redmine ruby] Issue #4139 has been updated by David Trusty.

^ [Ruby 1.9-Bug#4300][Open] Merge keys not working as expected in psych yaml parser
34679 [redmine ruby] Bug #4300: Merge keys not working as expected in psych yaml parser

^ [Ruby 1.9-Bug#4168] WeakRef is unsafe to use in Ruby 1.9
34680 [redmine ruby] Issue #4168 has been updated by Kurt  Stephens.

^ [Ruby 1.9-Bug#4168] WeakRef is unsafe to use in Ruby 1.9
34688 [redmine ruby] Issue #4168 has been updated by Charles Nutter.

^ [Ruby 1.9-Bug#3889][Closed] Incorrectly detected i686-w64-mingw32 as x64-mingw
34689 [redmine ruby] Issue #3889 has been updated by Luis Lavena.

^ [Ruby 1.9-Bug#4301][Open] Off-by-one line number in Psych parse error
34690 [redmine ruby] Bug #4301: Off-by-one line number in Psych parse error

^ [Ruby 1.9-Bug#4168] WeakRef is unsafe to use in Ruby 1.9
34691 [redmine ruby] Issue #4168 has been updated by Charles Nutter.

^ [Ruby 1.9-Bug#4294] IO.popen ['"ping"', 'localhost -n 3'] fails
34695 [redmine ruby] Issue #4294 has been updated by red stun.

^ [Ruby 1.9-Feature#4257] switch_hitter - an acceleration of date library
34696 [redmine ruby] Issue #4257 has been updated by Jeremy Evans.

^ rubycommitters.org contest
34697 [aaron tender] Recently I ran a contest to design a website for us.  You can read the

^ [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
34702 [redmine ruby] Issue #4239 has been updated by Zeno Davatz.
34706 [naruse airem] 87 as it used to work in Ruby 1.8.6 and in Ruby 1.9.1?

^ [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
34703 [redmine ruby] Issue #4239 has been updated by Zeno Davatz.
34707 [naruse airem] . It should not be a dead-end road to stable heaven. It should be a bridge =

^ [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
34708 [redmine ruby] Issue #4239 has been updated by Zeno Davatz.
+ 34713 [naruse airem] ration for 1.9.2 as it worked for 1.8.6 and 1.9.1 but does not work for 1.9=
+ 34765 [headius head] JRuby 1.8 and 1.9 modes (equivalent to 1.8.7 and 1.9.2) both reject
  34766 [headius head] I should also add that mutation-during-iteration has always been a

^ [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
34710 [redmine ruby] Issue #4239 has been updated by Zeno Davatz.

^ [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
34711 [redmine ruby] Issue #4239 has been updated by Zeno Davatz.
34715 [naruse airem] op-Down approach.

^ [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
34714 [redmine ruby] Issue #4239 has been updated by Zeno Davatz.
+ 34717 [naruse airem] ult bug to indeterminately fail to add a new key.
+ 34785 [duerst it.ao] In a separate thread, you claim that Ruby is inconsistent because it did

^ [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
34716 [redmine ruby] Issue #4239 has been updated by Zeno Davatz.
34719 [billk cts.co] I'm inclined to doubt Linus takes such a wait-and-see approach
34732 [naruse airem] Linux addresses all such potential instability?
34734 [billk cts.co] Greetings,

^ [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
34722 [redmine ruby] Issue #4239 has been updated by Zeno Davatz.
+ 34731 [naruse airem] ation at that is broken now as well because of some random If-Case that is =
+ 34733 [billk cts.co] Zeno,

^ [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
34723 [redmine ruby] Issue #4239 has been updated by Zeno Davatz.

^ [Ruby 1.9-Bug#4303][Open] Segmentation fault (using tarantula and hpricot)
34724 [redmine ruby] Bug #4303: Segmentation fault (using tarantula and hpricot)

^ [Ruby 1.9-Bug#4303][Feedback] Segmentation fault (using tarantula and hpricot)
34725 [redmine ruby] Issue #4303 has been updated by Shota Fukumori.

^ [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
34735 [redmine ruby] Issue #4239 has been updated by Zeno Davatz.
+ 34736 [luislavena g] dbi gem because the dbi-gem uses simple normal HashIteration to load Data f=
+ 34742 [matthias wae] Why don°«t you just fix ruby-dbi, upgrade ruby to 1.9.2 and continue life? ruby-dbi is broken misusing an inconsistency of 1.8.6°«s hash iteration. This

^ [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
34737 [redmine ruby] Issue #4239 has been updated by Zeno Davatz.
34738 [halostatue g] You're looking at 1.9.2 as if the version were major.minor.patch. It isn't, a=

^ Redmine spam
34739 [jonas pfenni] I really hate spammers, is it something we can do to prevent them
34741 [naruse airem] I lock outed those users, thanks.
34896 [jonas pfenni] mariah33z mariah33z
34897 [jonas pfenni] change items (since the change is not published in RSS format). Quite
35156 [jonas pfenni] All fresh from today, I list them so one day we can cleanup the wikis.
35163 [naruse airem] Thanks, locked and fixed those changes.

^ [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
34743 [redmine ruby] Issue #4239 has been updated by Zeno Davatz.
34755 [halostatue g] hould read. Ruby versioning seems one big book of secrets it seems.

^ [Ruby 1.9-Bug#4294] IO.popen ['"ping"', 'localhost -n 3'] fails
34746 [redmine ruby] Issue #4294 has been updated by Robert Klemme.

^ [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
34747 [redmine ruby] Issue #4239 has been updated by Zeno Davatz.
+ 34748 [luislavena g] to work with Ruby 1.8.6 and Ruby 1.9.1 - We just tested it with our Ruby 1=
+ 34749 [cremes.devli] Zeno,
+ 34750 [matz ruby-la] I have never seen "a complex system that use Oniguruma" instead of 1.8

^ [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
34751 [redmine ruby] Issue #4239 has been updated by Zeno Davatz.
34761 [meta pobox.c] I would suggest that you

^ Is evaluation order of arguments specified?
34752 [now bitwi.se] Is the evaluation order of arguments specified?  I couldn=E2=80=99t find
34759 [evan falling] The evaluation order is left to right. If there is not a rubyspec for =
34762 [now bitwi.se] that should be fixed.
34763 [evan falling] it, that should be fixed.

^ [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
34753 [redmine ruby] Issue #4239 has been updated by Zeno Davatz.

^ [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
34754 [redmine ruby] Issue #4239 has been updated by Zeno Davatz.

^ [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
34756 [redmine ruby] Issue #4239 has been updated by Zeno Davatz.
34757 [code jeremye] Correction, it does not work *with your app*.  All of your examples on

^ Re: Hash iteration contract (was Re: Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?)
34758 [meta pobox.c] I still think it's a bad idea to guarantee any particular ordering
+ 34764 [headius head] Java also provides LinkedHashMap, a hash-based map that preserves
+ 34767 [ruby-ml kitt] I agree, especially because a hash is by definition unordered.

^ [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
34768 [redmine ruby] Issue #4239 has been updated by Zeno Davatz.

^ [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
34769 [redmine ruby] Issue #4239 has been updated by Zeno Davatz.
+ 34770 [blambeau gma] Dear Zeno,
+ 34771 [meta pobox.c] Well, I said *ideally*. That word is important. One of the key goals

^ [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
34772 [redmine ruby] Issue #4239 has been updated by Zeno Davatz.
34774 [lucas lucas-] No, that did not confuse me. I do not confuse Ruby versioning with

^ [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
34773 [redmine ruby] Issue #4239 has been updated by Zeno Davatz.
34775 [matz ruby-la] So do you really mean to suggest throwing away our work of 8 years,

^ MRI 1.9 valgrind errors
34776 [ks kurtsteph] I've been drilling deep into MRI's gc.
+ 34778 [ks kurtsteph] Never mind.  This mark_current_machine_context() error is due to
| 34804 [naruse airem] Specify --with-valgrind to configure, and you can ignore such erros.
+ 34822 [mike.dalessi] When I'm running valgrind against MRI I use

^ [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
34777 [redmine ruby] Issue #4239 has been updated by Charles Nutter.

^ [Ruby 1.9-Bug#4301][Closed] Off-by-one line number in Psych parse error
34779 [redmine ruby] Issue #4301 has been updated by Anonymous.

^ [Ruby 1.9-Bug#4297][Closed] test_time in ruby/test/psych/test_json_tree.rb makes test failure
34780 [redmine ruby] Issue #4297 has been updated by Anonymous.

^ [Ruby 1.9-Bug#4300][Closed] Merge keys not working as expected in psych yaml parser
34781 [redmine ruby] Issue #4300 has been updated by Anonymous.

^ [Ruby 1.9-Bug#4301] Off-by-one line number in Psych parse error
34782 [redmine ruby] Issue #4301 has been updated by Charles Nutter.
34796 [aaron tender] yaml. The following version has the *correct* line number, without your pat=

^ [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
34783 [redmine ruby] Issue #4239 has been updated by Zeno Davatz.

^ [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
34784 [redmine ruby] Issue #4239 has been updated by Zeno Davatz.
+ 34786 [rr.rosas gma] Zeno, you seem to take a lot of wrong assumptions about Ruby developers.
+ 34792 [drbrain segm] ost popular gems and their maintainers, that you consult _before_ you releas=

^ [Ruby 1.9-Bug#4298] Duration of calling String#[] with the same index is strangely related to string length.
34787 [redmine ruby] Issue #4298 has been updated by Heesob Park.

^ [Ruby 1.9-Bug#4303] Segmentation fault (using tarantula and hpricot)
34788 [redmine ruby] Issue #4303 has been updated by Markus Bengts.

^ [Ruby 1.9-Bug#4306][Open] psych makes a lot of test failure on Win32 build
34791 [redmine ruby] Bug #4306: psych makes a lot of test failure on Win32 build
34798 [aaron tender] tform.

^ [Ruby 1.9-Bug#4298] Duration of calling String#[] with the same index is strangely related to string length.
34793 [redmine ruby] Issue #4298 has been updated by Charles Nutter.
+ 34799 [matz ruby-la] RSTRING_LEN is the byte length of the string, but we can assume
+ 34800 [phasis gmail] ? Isn't that always guaranteed to be >=3D str_strlen, which is the characte=

^ [Ruby 1.8-Feature#4239] Let's begin a talk for "1.8.8" -- How's needed for surviving 1.8?
34794 [redmine ruby] Issue #4239 has been updated by Zeno Davatz.
34795 [cezary.bagin] do_something_with_encoding if defined?(Encoding)

^ [Ruby 1.9-Bug#4301][Open] Off-by-one line number in Psych parse error
34797 [redmine ruby] Issue #4301 has been updated by Aaron Patterson.

^ [Ruby 1.9-Bug#4298][Closed] Duration of calling String#[] with the same index is strangely related to string length.
34801 [redmine ruby] Issue #4298 has been updated by Nobuyoshi Nakada.

^ [Ruby 1.9-Bug#4306][Rejected] psych makes a lot of test failure on Win32 build
34802 [redmine ruby] Issue #4306 has been updated by Motohiro KOSAKI.

^ [Ruby 1.9-Bug#4009] Segfault with combination of threads and condition variables
34805 [redmine ruby] Issue #4009 has been updated by Max Aller.
34875 [mame tsg.ne.] =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=

^ [Ruby 1.9-Bug#4307][Open] include fails after undef_method
34806 [redmine ruby] Bug #4307: include fails after undef_method
34807 [lsegal soen.] This seems like expected behaviour to me.

^ [Ruby 1.9-Bug#4301] Off-by-one line number in Psych parse error
34808 [redmine ruby] Issue #4301 has been updated by Charles Nutter.
threads.html
top