[#66126] Creation/Conversion methods/functions table for Ruby types — SASADA Koichi <ko1@...>
Hi,
5 messages
2014/11/07
[#66248] [ruby-trunk - Feature #10423] [PATCH] opt_str_lit*: avoid literal string allocations — normalperson@...
Issue #10423 has been updated by Eric Wong.
3 messages
2014/11/13
[#66595] [ruby-trunk - Bug #10557] [Open] Block not given when the argument is a string — bartosz@...
Issue #10557 has been reported by Bartosz Kopinski.
3 messages
2014/11/30
[ruby-core:66046] [ruby-trunk - Bug #10454] %i doesn't have any special behavior in rb_sprintf et al.
From:
silverhammermba+ruby@...
Date:
2014-11-01 15:49:10 UTC
List:
ruby-core #66046
Issue #10454 has been updated by Max Anselm. Ah, I see now. I needed to use `%li`. It seems like README.EXT should mention `PRIsVALUE` instead of `%i`. ---------------------------------------- Bug #10454: %i doesn't have any special behavior in rb_sprintf et al. https://bugs.ruby-lang.org/issues/10454#change-49767 * Author: Max Anselm * Status: Closed * Priority: Normal * Assignee: Zachary Scott * Category: doc * Target version: * ruby -v: ruby 2.1.4p265 (2014-10-27 revision 48166) [x86_64-linux] * Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN ---------------------------------------- README.EXT claims: > In the format string, `%i` is used for `Object#to_s` (or `Object#inspect` if ‘+’ flag is set) output (and related argument must be a VALUE). But if you look at the code, this isn't true. %d and %i are handled the same in `BSD_vfprintf` (which is where all the printf functions end up). Has this ever been the case? I went back to when this documentation was added and it still looks like they're handled the same. -- https://bugs.ruby-lang.org/