[#35027] [Ruby 1.9-Bug#4352][Open] [patch] Fix eval(s, b) backtrace; make eval(s, b) consistent with eval(s) — "James M. Lawrence" <redmine@...>
Bug #4352: [patch] Fix eval(s, b) backtrace; make eval(s, b) consistent with eval(s)
Issue #4352 has been updated by James M. Lawrence.
Hi,
On Wed, Feb 2, 2011 at 10:47 AM, Yusuke ENDOH <mame@tsg.ne.jp> wrote:
Hi,
[#35036] [Ruby 1.9-Bug#4354][Open] File.realdirpath is expected to test for real file. — Luis Lavena <redmine@...>
Bug #4354: File.realdirpath is expected to test for real file.
[#35055] [Ruby 1.9-Bug#4359][Open] regular expressions created with Regexp::FIXEDENCODING have incorrect inspect — Aaron Patterson <redmine@...>
Bug #4359: regular expressions created with Regexp::FIXEDENCODING have incorrect inspect
[#35071] Bug in system()? — Anthony Wright <anthony@...>
I've just hit a problem where the system() method to call an external program failed in a fairly unpredictable way, and I couldn't get any clues from within ruby to diagnose the problem. As a result I ended up debugging process.c to work out what the problem was.
[#35100] [Ruby 1.9-Bug#4370][Open] Abort trap in net/http — David Phillips <redmine@...>
Bug #4370: Abort trap in net/http
[#35114] [Ruby 1.9-Bug#4373][Open] http.rb:677: [BUG] Segmentation fault — Christian Fazzini <redmine@...>
Bug #4373: http.rb:677: [BUG] Segmentation fault
[#35144] Documentation Clarifications to Array methods rotate, rotate!, index, and rindex — Loren Sands-Ramshaw <lorensr@...>
Tue Feb 8 11:47:11 2011 Loren Sands-Ramshaw <lorensr@gmail.com>
[#35146] [Ruby 1.9-Bug#4383][Assigned] psych fails to parse a symbol in a flow sequence — Yuki Sonoda <redmine@...>
Bug #4383: psych fails to parse a symbol in a flow sequence
[#35167] Redmine misconfigured (was Re: Re: [Ruby 1.9-Bug#4340] Encoding of result string for String#gsub is not consistent) — mathew <meta@...>
On Tue, Feb 8, 2011 at 16:27, Eric Hodel <drbrain@segment7.net> wrote:
[#35171] [Ruby 1.9-Bug#4386][Open] encoding: directive does not affect regex expressions — mathew murphy <redmine@...>
Bug #4386: encoding: directive does not affect regex expressions
[#35202] Patch to Net::InternetMessageIO — Daniel Cormier <daniel.cormier@...>
This patch addresses an issue when sending a message with Net::SMTP
On Fri, Feb 11, 2011 at 09:13, Daniel Cormier <daniel.cormier@gmail.com> wrote:
Perhaps that is a better solution, but shouldn't sending a message
On Fri, Feb 11, 2011 at 17:08, Daniel Cormier <daniel.cormier@gmail.com> wrote:
Ok, but since the period escaping is already being done (just with
[#35237] [Ruby 1.9-Bug#4400][Open] nested at_exit hooks run in strange order — Suraj Kurapati <redmine@...>
Bug #4400: nested at_exit hooks run in strange order
Issue #4400 has been updated by Motohiro KOSAKI.
[#35332] [ANN] Planned maintenance of redmine.ruby-lang.org — "Yuki Sonoda (Yugui)" <yugui@...>
-----BEGIN PGP SIGNED MESSAGE-----
-----BEGIN PGP SIGNED MESSAGE-----
[#35340] odd require behavior — Roger Pack <rogerdpack2@...>
Hello all.
[#35355] eval'ing large strings runs out of stack space? — Roger Pack <rogerdpack2@...>
Hello all.
[#35356] suggestion: default irb to saving history — Roger Pack <rogerdpack2@...>
Hello all.
[#35376] [Ruby 1.9 - Feature #4447] [Open] add String#byteslice() method — Suraj Kurapati <sunaku@...>
string.force_encoding(ENCODING::BINARY).slice almost does what you want,
[ruby-core:35113] Re: [Ruby 1.9-Bug#4343] Dir.glob does match files without extension
mathew, First of all, let me assure that I'm well aware of engineering trade offs. I suggested that consistency be maintained where feasible, not always and at the expense of sanity. I also suggested that extensions would be useful if there was demand, such as adding support for Windows-style globbing. I don't want Ruby put into a straight jacket, but I also don't want to make it needlessly difficult for Ruby developers to get their work done. Your examples of managing filesystem case-sensitivity all have major shortcomings to interoperability with non-Ruby programs when only used within Ruby itself. Two of your solutions are used by file servers that present a single filesystem level interface to all programs. They can get away with the hacks they perform because all programs use the hacked side of the interface. Going behind the file server's back can cause trouble actually. The third solution only provides a sorting mechanism for file lists and does not describe a way to store and retrieve file data given a file path. If Ruby tried to enforce a lowest common denominator filesystem approach of any kind, Ruby programs would appear broken to the users who need interoperability with non-Ruby programs. Few developers would use it as a result, and you'll note that not even Java attempts to do such a foolish thing. You'll likely argue that Ruby having its own globbing solution appears similarly broken. My counter is that end users do not use globbing enough within Ruby to warrant the extra support load on Ruby developers who would need to be cognizant of the differences for each platform. Users' use of globbing will usually be limited to the command line where globbing is already handled in a platform-specific way outside of the Ruby script. I further contend that developers are more than capable of learning Ruby's implementation and tend to appreciate the fact that they don't have to worry about differences in implementation per platform. Consider yourself lucky that you only need to support a single platform with your scripts. I'm pleased to escape the old days of non-portable C code and endless #ifdefs. If you think I'm misguided or an aberration, ponder the reasons for the existence of Gnulib, APR, libiberty, and similar abstraction libraries. -Jeremy