22249-23532

22013-22844 subjects 22586-23080

[Bug #1091](Closed) possible bad handling of return value of OCSP_basic_verify in ext/openssl/ossl_ocsp.c
22249 [redmine@ru y] Issue #1091 has been updated by Nobuyoshi Nakada.

[Bug #1177] eof for socket block script
22258 [redmine@ru y] Bug #1177: eof for socket block script
22282 [nobu@ru y- a] Could you show the reproduceable code?

[Bug #1178] circular dependency on missing ffi
22260 [redmine@ru y] Bug #1178: circular dependency on missing ffi

[Bug #1180] gethostbyname
22261 [redmine@ru y] Bug #1180: gethostbyname
22290 [nobu@ru y- a] Is what you want Socket.getnameinfo?

[Bug #1181] [BUG] thread_free: keeping_mutexes must be NULL
22269 [redmine@ru y] Bug #1181: [BUG] thread_free: keeping_mutexes must be NULL
22279 [mame@ts .n .] al error messages. The applications runs fine with ruby 1.8.7. I tried to c=
22292 [mame@ts .n .] nal error messages. The applications runs fine with ruby 1.8.7. I tried to =
+ 22350 [cschlaeger@g] I can confirm that your patch fixes the problem. Thanks for your quick help!
+ 22351 [matz@ru y- a] Please check in.

[Bug #405] ssl.rb:31: [BUG] Bus Error
22271 [redmine@ru y] Issue #405 has been updated by Matt G.
22546 [rogerdpack@g] what versions of openssl are you using?

[Bug #1178](Feedback) circular dependency on missing ffi
22276 [redmine@ru y] Issue #1178 has been updated by Nobuyoshi Nakada.

[Bug #1180](Feedback) gethostbyname
22277 [redmine@ru y] Issue #1180 has been updated by Nobuyoshi Nakada.

[Bug #1182] REXML::Source#position badly implemented and other related issues
22284 [redmine@ru y] Bug #1182: REXML::Source#position badly implemented and other related issues

[Backport #1183] Adding support for the new hash literal syntax
22286 [redmine@ru y] Backport #1183: Adding support for the new hash literal syntax
22288 [nobu@ru y- a] No such syntax has been defined officially.
22289 [shyouhei@ru ] What do you mean here in "official"? because AFAIK there has been no single
22291 [nobu@ru y- a] Matz's book and official tutorial[1] mention about "then" but
22293 [shyouhei@ru ] At least O'Reilly's "Programming Language Ruby" has a detailed description

[Bug #1164](Closed) 1.9/windows memroy leak with rand() AND inspect
22294 [redmine@ru y] Issue #1164 has been updated by Usaku NAKAMURA.

[Bug #1184] Type error in Integer#to_bn (via Openssl)
22297 [redmine@ru y] Bug #1184: Type error in Integer#to_bn (via Openssl)

[Bug #1185] Segfault after removal of method_missing
22298 [redmine@ru y] Bug #1185: Segfault after removal of method_missing

[Bug #1186] :method_missing not shown as an instance_method of BasicObject
22299 [redmine@ru y] Bug #1186: :method_missing not shown as an instance_method of BasicObject

[Bug #725](Assigned) Synchronized block in finalizer-method results in deadlock/ crash of the interpreter
22301 [redmine@ru y] Issue #725 has been updated by Nobuyoshi Nakada.

wish list item: rconsole
22304 [rogerdpack@g] After using jvm a bit, I'll admit it has a few things of which I am jealous.
22318 [wycats@gm il] What about http://rubyforge.org/projects/live-console/ ?
22319 [rogerdpack@g] That's pretty cool.  ruby-debug has remote access, as well, now that I

[Bug #1186] :method_missing not shown as an instance_method of BasicObject
22305 [redmine@ru y] Issue #1186 has been updated by Lin Jen-Shin.

1.8.7 make check question
22308 [rogerdpack@g] Currently, it seems that if I run

[Bug #1190] irb's "help" command errs in 1.9
22310 [redmine@ru y] Bug #1190: irb's "help" command errs in 1.9

options for previous versions downloads?
22314 [rogerdpack@g] currently on http://www.ruby-lang.org/en/downloads/ there are
22596 [rogerdpack@g] A link from

[Bug #1185](Closed) Segfault after removal of method_missing
22321 [redmine@ru y] Issue #1185 has been updated by Nobuyoshi Nakada.

[Backport #962](Closed) Patch for Makefile rubyspec rules after 1.8/1.9 spec merge
22324 [redmine@ru y] Issue #962 has been updated by Shyouhei Urabe.

suggestions for float
22325 [rogerdpack@g] Floating point rounding errors are common and "annoying"
+ 22595 [rogerdpack@g] I guess there's not too much feedback on this one :)
| 22621 [matz@ru y- a] We are not ignoring you.  We just lack for resource working on the
| + 22623 [phasis@gm il] #define LUA_NUMBER_FMT		"%.14g"
| | 22630 [nobu@ru y- a] Marshal also has such code.
| | 22676 [matz@ru y- a] Could you check in?
| + 22624 [ruby-ml@ki t] The most user-friendly solution would likely be to go BigDecimal
|   22629 [kurt@ca hn t] ...
|   22631 [ruby-ml@ki t] I am personally concerned about formatting floats, but their
|   22632 [rogerdpack@g] Is that code good enough or should we fix it at "x" digits?  I'd
|   22638 [brent@mb ri ] OK.  I apologize in advance.  Soapbox on...
|   + 22639 [phasis@gm il] class Float
|   + 22705 [rogerdpack@g] =3D> -0.9
|   | + 22709 [dev@me ne .c] Again, what about something like Python's?
|   | | 22710 [lukfugl@gm i] s puts
|   | | 22712 [brent@mb ri ] +1
|   | + 22713 [brent@mb ri ] # return true if other (Numeric) is approximately equal
|   + 22721 [charles.nutt] I've been forced to argue this point many times because Ruby gives the
|     22791 [meta@po ox c] I agree.
|     22796 [vjoel@pa h. ] So why not define a FixedPoint class, based on Integer, with all the
|     + 22798 [ruby-ml@ki t] Or we could all just use Rational :)
|     + 22806 [brent@mb ri ] Numbers in various formats are well supported by Ruby, but, for many of them,
+ 22626 [dev@me ne .c] Perhaps we could have distinct Float#to_s and #inspect, like Python?

[Bug #1192] encoding problem with tr() and hash keys 1.9.1
22326 [redmine@ru y] Bug #1192: encoding problem with tr() and hash keys 1.9.1

[Bug #1192](Closed) encoding problem with tr() and hash keys 1.9.1
22327 [redmine@ru y] Issue #1192 has been updated by Nobuyoshi Nakada.

[Bug #1192](Open) encoding problem with tr() and hash keys 1.9.1
22328 [redmine@ru y] Issue #1192 has been updated by Yusuke Endoh.

[Bug #1192](Closed) encoding problem with tr() and hash keys 1.9.1
22329 [redmine@ru y] Issue #1192 has been updated by Nobuyoshi Nakada.

[PATCH] Support for COLORS and COLOR_PAIRS in ext/curses
22331 [Alexander.Be] ...

[Feature #1193] Justified Error Messages
22333 [redmine@ru y] Feature #1193: Justified Error Messages
22408 [matz@ru y- a] Your proposal seems reasonable, but since Ryan rejected (and he is the

Hash, eql and builtin subclass issue
22335 [lopx@ga et .] class X < String

Floats are freezeable and taintable?
22336 [charles.nutt] In adding an optimization for Float I realized that Float objects are
+ 22337 [brent@mb ri ] I'm pretty sure that it is a consequence of Floats not being immediate
| 22340 [charles.nutt] Yes, that would be desirable, if there's not a good reason they aren't
| 22354 [duerst@it ao] The main reason they are not immediates now is that they do not fit
| 22357 [charles.nutt] Perhaps we should start pretending they're immediates now, and specify
| 22382 [kurt@ca hn t] Tag bits in the LSB of the mantissa?  Loss of C double/float precision?
| 22385 [charles.nutt] Ask ko1 :) I do not know. I'm only interested in not having to support
| 22387 [gwtmp01@ma .] It seems like this is a strange corner case with the language.
+ 22677 [matz@ru y- a] Since they are plain objects, but we do guarantee no identity for any
  22690 [charles.nutt] Other than making freeze and taint (and untrust on 1.9) behave the same
  22691 [matz@ru y- a] * making all immediate values frozen
  22693 [charles.nutt] That seems fine to me. I assume this would mean you can no longer have
  22694 [matz@ru y- a] Correct.

[Bug #1194] Unable to compile 1.9.1-p0 under Windows with Visual Studio 2008 Express
22339 [redmine@ru y] Bug #1194: Unable to compile 1.9.1-p0 under Windows with Visual Studio 2008 Express

[Bug #1194] Unable to compile 1.9.1-p0 under Windows with Visual Studio 2008 Express
22342 [redmine@ru y] Issue #1194 has been updated by Charlie Savage.

[Bug #1162] Build Assertion Failure with VC+++ - Incorrect flushing of stdout/stderr
22345 [redmine@ru y] Issue #1162 has been updated by Charlie Savage.
22352 [nobu@ru y- a] You are wrong about -RTC1.  It does emit checking code but

String encoding in the C api
22346 [aaron@te de ] Is there an easy way to set my string enoding from the C api?
22348 [nobu@ru y- a] VALUE rb_enc_str_new(const char*, long, rb_encoding*);
22349 [aaron@te de ] Rock and roll.

On the consideration of macros
22347 [quixoticsyco] In a previous thread Charles Oliver Nutter had suggested the removal
+ 22381 [brent@mb ri ] Thanks for this detailed, well reasoned post.
| 22402 [quixoticsyco] of
+ 22398 [charles.nutt] Very intriguing! I think the use of ruby_parser is probably the best
  + 22399 [billk@ct .c ] ...it would also eliminate my need for Binding.of_caller    ;)
  | 22401 [charles.nutt] I'm sold :)
  + 22403 [wycats@gm il] Matz has repeatedly and explicitly expressed that he did not want Ruby to
    22407 [quixoticsyco] I have been specifically talking about a simple string-based macro
    22562 [joergwmittag] Ruby to

[Bug #1195] String#% does not include prefix before zero value for # versions of numeric formats
22353 [redmine@ru y] Bug #1195: String#% does not include prefix before zero value for # versions of numeric formats
22397 [akr@fs j. rg] It's intentional.
22400 [charles.nutt] So then the Ruby 1.8 behavior is a bug. Can we move the bug to Ruby 1.8?
+ 22404 [akr@fs j. rg] I'm not sure Ruby 1.8 behavior is a bug or a spec.
+ 22405 [knu@iD em ns] When 0b0, 0B0, 00, 0x0, and 0X0 are all perfectly human readable and
  22406 [charles.nutt] We implemented our own sprintf that matches Ruby (and in places, C)
  22411 [matz@ru y- a] Ruby 1.8 uses underlying sprintf() where 1.9 uses its own
  22421 [charles.nutt] Given that, I think leaving it specified as a new behavior in 1.9 is
  22429 [matz@ru y- a] It's up to you.  1.8 behavior is not a bug, it's just one of
  22432 [charles.nutt] Thank you for the clarification. I'll talk with Brian about how best to

[Bug #1197] regular expression never finishes
22361 [redmine@ru y] Bug #1197: regular expression never finishes

[Bug #1197](Rejected) regular expression never finishes
22363 [redmine@ru y] Issue #1197 has been updated by Shyouhei Urabe.

Surprising behavior in inheritance
22365 [now@bi wi se] Am I the only one surprised by this behavior?
+ 22366 [dblack@ru yp] I'm not surprised by it. I figure access level is per method per class,
+ 22367 [matz@ru y- a] The visibility of a method is not inherited by spec.
+ 22368 [ruby-ml@ki t] You overrode the inherited method with a public one. Seems correct?
  22371 [now@bi wi se] Yes, that's perhaps what some would expect, but certainly not what I'd
  22376 [ruby-ml@ki t] Visibility specifiers only affect the Module in which they appear,

[Bug #1197] regular expression never finishes
22370 [redmine@ru y] Issue #1197 has been updated by Yui NARUSE.

[Bug #1181](Closed) [BUG] thread_free: keeping_mutexes must be NULL
22373 [redmine@ru y] Issue #1181 has been updated by Yusuke Endoh.

Proposal: Integer.digit_count
22383 [thevarungupt] How about having a method to return number of digits in the Integer?
22384 [wycats@gm il] What's the use-case for this being in the language? It's damn easy to write
22386 [kurt@ca hn t] ...
22388 [jimfreeze@gm] abs.to_s.size
22389 [flo@an er gr] ...

[Bug #1194] Unable to compile 1.9.1-p0 under Windows with Visual Studio 2008 Express
22391 [redmine@ru y] Issue #1194 has been updated by Alexandre Vaillancourt.

[Proposal]Possibility for using named and normal groups together in regular expressions
22412 [ed.odanow@wo] Dear Ruby and Oniguruma developers!

[Proposal]Add relative group reference in back reference with nest level in regular expressions (e.g. \k<-5+1>)
22413 [ed.odanow@wo] Dear Ruby and Oniguruma developers!
22556 [ed.odanow@wo] I have an additional question. Is Oniguruma still under development or

[Bug #1199] wrong coderange in multiple String methods
22414 [redmine@ru y] Bug #1199: wrong coderange in multiple String methods

[Feature #1200] Possibility for using named and normal groups together in regular expressions
22415 [redmine@ru y] Feature #1200: Possibility for using named and normal groups together in regular expressions

[Feature #1201] Add relative group reference in back reference with nest level in regular expressions (e.g. \k<-5+1>)
22416 [redmine@ru y] Feature #1201: Add relative group reference in back reference with nest level in regular expressions (e.g. \k<-5+1>)

[Feature #1200] Possibility for using named and normal groups together in regular expressions
22417 [redmine@ru y] Issue #1200 has been updated by Wolfgang N叩dasi-Donner.

[Question]utf-8 data contains BOM - by intention or by accident?
22418 [ed.odanow@wo] One short question. When I'm reading an utf-8 encoded file (Windows,
22461 [duerst@it ao] I don't think there are any plans to build in BOM recognition or
22464 [ed.odanow@wo] There were discusions about this point end of 2007, but several encoding
22468 [matz@ru y- a] y  intention or by accident?"
22475 [shyouhei@ru ] And what's going on with that plan? I think it's your move, matz.
22477 [matz@ru y- a] I know.  I haven't decided to accept API shown in #802.  It's OK if
22479 [shyouhei@ru ] OK, make a better API.  But can I set its target to 1.9.2?
22482 [matz@ru y- a] Ah, yes...

[Bug #1199](Closed) wrong coderange in multiple String methods
22420 [redmine@ru y] Issue #1199 has been updated by Nobuyoshi Nakada.

[Bug #1202] mongrel-1.1.5-x86-mswin32-60 error
22425 [redmine@ru y] Bug #1202: mongrel-1.1.5-x86-mswin32-60 error
22428 [luislavena@g] Mongrel 1.1.5 has not been updated to work with 1.9.1

[Bug #1203] IO#gets ignores the limit parameter when sep is nil
22434 [redmine@ru y] Bug #1203: IO#gets ignores the limit parameter when sep is nil

[Bug #1204] Bug in String#force_encoding?
22437 [redmine@ru y] Bug #1204: Bug in String#force_encoding?

[Bug #1205] SET_STACK_END crashes due to uninitialized ruby_current_thread
22439 [redmine@ru y] Bug #1205: SET_STACK_END crashes due to uninitialized ruby_current_thread
22535 [nobu@ru y- a] Isn't the stack direction on Android defined statically?

[Bug #1203](Closed) IO#gets ignores the limit parameter when sep is nil
22443 [redmine@ru y] Issue #1203 has been updated by Nobuyoshi Nakada.

[Bug #1204](Closed) Bug in String#force_encoding?
22444 [redmine@ru y] Issue #1204 has been updated by Nobuyoshi Nakada.

[Bug #1194](Closed) Unable to compile 1.9.1-p0 under Windows with Visual Studio 2008 Express
22445 [redmine@ru y] Issue #1194 has been updated by Nobuyoshi Nakada.

[Feature #1206] New unit test runner: Test::Unit::UI::Xml::TestRunner
22458 [redmine@ru y] Feature #1206: New unit test runner: Test::Unit::UI::Xml::TestRunner

[Bug #1207] Readline#readline mangles input
22463 [redmine@ru y] Bug #1207: Readline#readline mangles input

[Bug #1207] Readline#readline mangles input
22465 [redmine@ru y] Issue #1207 has been updated by Tero Tilus.

[Bug #1210] Array behavior for minus/uniq is not as expected for hash elements
22472 [redmine@ru y] Bug #1210: Array behavior for minus/uniq is not as expected for hash elements

[Feature #1212] doc for Array#fill misses indication about negative value for the start argument
22497 [redmine@ru y] Feature #1212: doc for Array#fill misses indication about negative value for the start argument

ArgumentError when comparing a Fixnum with BigDecimal("NaN")
22504 [Shri.Borde@m] Ruby 1.8.6 and 1.9 both raise an ArgumentError when comparing a Fixnum with=

[Bug #1214] Build issues
22520 [redmine@ru y] Bug #1214: Build issues
22536 [nobu@ru y- a] It has been fixed in the trunk already last week.

[Bug #1207] Readline#readline mangles input
22534 [redmine@ru y] Issue #1207 has been updated by Tero Tilus.

[Bug #814] NoMethodError: undefined method `read_nonblock' for #<OpenSSL::SSL::SSLSocket:0x1a64f9a0>
22538 [redmine@ru y] Issue #814 has been updated by Tony Arcieri.
22539 [akr@fs j. rg] Does it care the I/O buffer implemented in
22802 [tony@me io .] I'm not certain.  What exactly does this do?
22807 [akr@fs j. rg] Assume gets and read_nonblock is used as follows.
22830 [tony@me io .] All right, as soon as you've finalized the exception names I will use those
22837 [akr@fs j. rg] It force people to rescue IO::WantRead instead of
23532 [tony@me io .] them in the openssl-nonblock gem.

[Feature #1218] New method needed to set and get the current recursion limit
22543 [redmine@ru y] Feature #1218: New method needed to set and get the current recursion limit

[Feature #1218] New method needed to set and get the current recursion limit
22545 [redmine@ru y] Issue #1218 has been updated by Dave B.
22551 [jdeville@mi ] That wouldn't help for Ruby on Windows. It would also be nice to have something tied to the code, not the system.

[Bug #1219] ostruct freeze still not stable
22559 [redmine@ru y] Bug #1219: ostruct freeze still not stable

[Bug #1220] DRb::Observable notify_observers
22560 [redmine@ru y] Bug #1220: DRb::Observable notify_observers

[Bug #1219] ostruct freeze still not stable
22561 [redmine@ru y] Issue #1219 has been updated by Robert Dober.

[Bug #1219](Closed) ostruct freeze still not stable
22564 [redmine@ru y] Issue #1219 has been updated by Nobuyoshi Nakada.
22644 [robert.dober] Thank you, very nice solution.

[Bug #1205](Closed) SET_STACK_END crashes due to uninitialized ruby_current_thread
22566 [redmine@ru y] Issue #1205 has been updated by Nobuyoshi Nakada.

[Bug #877](Rejected) [win32] Ruby Standard Library (maybe smth else): Wrong Encoding in Files, Directories and Environment Variables
22568 [redmine@ru y] Issue #877 has been updated by Usaku NAKAMURA.

[Bug #670] select doesn't handle fd's > FD_SETSIZE very well
22569 [redmine@ru y] Issue #670 has been updated by Usaku NAKAMURA.

[Bug #670] select doesn't handle fd's > FD_SETSIZE very well
22573 [redmine@ru y] Issue #670 has been updated by Roger Pack.

[Bug #1214] Build issues
22576 [redmine@ru y] Issue #1214 has been updated by hiro sugawara.
22923 [nobu@ru y- a] ruby-devに移動します。

[Bug #1205] SET_STACK_END crashes due to uninitialized ruby_current_thread
22577 [redmine@ru y] Issue #1205 has been updated by hiro sugawara.

[Bug #1223] Memory leak reintroduced in 1.8.6 branch?
22578 [redmine@ru y] Bug #1223: Memory leak reintroduced in 1.8.6 branch?
+ 22579 [giuseppe.bil] p238
+ 22581 [akr@fs j. rg] It seems 1.8.6p296 has a problem.
  22582 [billk@ct .c ] Ahh... thank you!! :D

[Bug #1223] Memory leak reintroduced in 1.8.6 branch?
22580 [redmine@ru y] Issue #1223 has been updated by B Kelly.

[Bug #1142] /opt/ruby19/lib/ruby19/1.9.1/openssl/ssl.rb:31: [BUG] Bus Error
22583 [redmine@ru y] Issue #1142 has been updated by Rick Lloyd.

MBARI8 patch fixes bugs caused by incorrect volatile variable declarations
22584 [brent@mb ri ] I believe I discovered two latent MRI bugs that had been unearthed by my
+ 22587 [nobu@ru y- a] Thank you, I consider you're correct, and merged into the 1.8
| + 22590 [akr@fs j. rg] gcc -O -W warns it.
| | 22599 [brent@mb ri ] Tanaka,
| | 22667 [kingmt@gm il] I am having an issue with the MBARI patches. In our app the test suite has a
| | + 22668 [brent@mb ri ] Michael,
| | | 22682 [kingmt@gm il] I am seeing the segfault with stack clearing set to both default level and
| | + 22669 [rogerdpack@g] a back trace and ruby -v would be nice.
| |   22681 [kingmt@gm il] by back trace do you mean the output of
| |   22686 [brent@mb ri ] Michael,
| |   22688 [kingmt@gm il] gdb -core core
| |   22689 [brent@mb ri ] Michael,
| |   22702 [kingmt@gm il] Its been way too long since I have used gdb, and I haven't ever had to look
| |   22714 [brent@mb ri ] Michael,
| + 22598 [brent@mb ri ] The comment about preventing tail call optimization was copied from another
+ 22683 [kingmt@gm il] A coworker of mine is working on his masters thesis using Ruby and some C
threads.html
top