[#21709] [Feature #1084] request for: Array#sort_by! — Radosław Bułat <redmine@...>
Feature #1084: request for: Array#sort_by!
Hi,
Issue #1084 has been updated by Yukihiro Matsumoto.
Excerpts from Henri Suur-Inkeroinen's message of Mon Feb 02 12:46:52 +0200 2009:
Eero Saynatkari wrote:
Excerpts from Kornelius Kalnbach's message of Mon Feb 02 13:32:33 +0200 2009:
Eero Saynatkari wrote:
[#21714] [BUG:trunk] Got the error message, after run 'gem install --test'. — Takao Kouji <kouji@...7.net>
Hi, Ryan.
Issue #1085 has been updated by Yusuke Endoh.
[#21715] New documentation system! — Luiz Vitor Martinez Cardoso <grabber@...>
People,
On Sun, Feb 1, 2009 at 10:51 AM, Luiz Vitor Martinez Cardoso
Quoting Austin Ziegler <halostatue@gmail.com>:
People,
One project that has been in the works for a while and shows a lot of
I'd love to see a documentation system similar to what python has, and
People,
Luiz Vitor Martinez Cardoso wrote:
=20
On Mon, Feb 2, 2009 at 10:31 AM, Berger, Daniel <Daniel.Berger@qwest.com> wrote:
On Mon, Feb 02, 2009 at 12:51:54AM +0900, Luiz Vitor Martinez Cardoso wrote:
> I like docstrings. I like being able to type "help(foo)" in python and
2009/2/14 Roger Pack <rogerdpack@gmail.com>:
> irb(main):002:0> help "String#chars"
[#21737] [Feature #1089] Stable sorting for sort and sort_by — Kornelius Kalnbach <redmine@...>
Feature #1089: Stable sorting for sort and sort_by
Kornelius Kalnbach wrote:
[#21747] [Bug #1090] zlib doesn't load after installation — Jérôme Bousquié <redmine@...>
Bug #1090: zlib doesn't load after installation
[#21762] [Bug #1091] possible bad handling of return value of OCSP_basic_verify in ext/openssl/ossl_ocsp.c — Lucas Nussbaum <redmine@...>
Bug #1091: possible bad handling of return value of OCSP_basic_verify in ext/openssl/ossl_ocsp.c
[#21764] ruby 1.9.1 in mingw - how to remove "-s" argument from gcc linking — Tim Elliott <tle@...>
I want to use gdb to debug an application that embeds the ruby dll.
Hi,
[#21802] [Bug #1098] Unclear encoding error: #<Encoding::UndefinedConversionError: "\xE2\x96\x80" from UTF-8 to ISO-8859-1 in conversion from CP850 to ISO-8859-1> — Tom Link <redmine@...>
Bug #1098: Unclear encoding error: #<Encoding::UndefinedConversionError: "\xE2\x96\x80" from UTF-8 to ISO-8859-1 in conversion from CP850 to ISO-8859-1>
[#21812] 1.9 Bug Report — Yehuda Katz <wycats@...>
When going through the RubySpecs for 1.9, I found that the following code
[#21822] [Feature #1102] Prepend Module — Thomas Sawyer <redmine@...>
Feature #1102: Prepend Module
[#21838] What does this regexp mean - /\c#{_J}/ — Shri Borde <Shri.Borde@...>
I am combining the escaped control character syntax (\cX) with variable int=
QWN0dWFsbHksIHdpdGggc3RyaW5ncywgdGhlIHJlZ2V4cCBpcyBldmFsdWF0ZWQgYXQgdGhlIHZl
[#21842] Regexp interpolation does not give equality — Shri Borde <Shri.Borde@...>
Any idea why the second expression results in false? Its seems like both th=
[#21855] [Bug #1113] Compilation fails on Ubuntu 8.10, 64 bit — Jacques Lemire <redmine@...>
Bug #1113: Compilation fails on Ubuntu 8.10, 64 bit
[#21880] [Bug #1117] Array#choice always produces the same sequence — Stefano Crocco <redmine@...>
Bug #1117: Array#choice always produces the same sequence
[#21884] [Bug #1118] irb core dumps with 'CTRL-C' with zsh — Emiel van de Laar <redmine@...>
Bug #1118: irb core dumps with 'CTRL-C' with zsh
[#21886] mule-utf-8 — Roman Shterenzon <romanbsd@...>
[#21893] [Feature #1122] request for: Object#try — Narihiro Nakamura <redmine@...>
Feature #1122: request for: Object#try
Hi,
Hi --
Hi,
Hi--
Hi,
Hi --
Providing new syntax change for such a small thing is IMHO
Count me in as a +1 on foo.?bar(baz). I'm on the fence about whether ?bar
2009/2/15 Yehuda Katz <wycats@gmail.com>:
> IMHO, foo.?bar should behave as "call-except-if-nil". Not only it
On Wed, Feb 18, 2009 at 6:29 PM, Roger Pack <rogerdpack@gmail.com> wrote:
> Then how it is different from
Roger Pack wrote:
>>> Then how it is different from
Roger Pack wrote:
On Wed, Feb 18, 2009 at 2:35 PM, Joel VanderWerf
Roger Pack wrote:
2009/2/19 Joel VanderWerf <vjoel@path.berkeley.edu>:
[#21903] [Bug #1127] error while compiling Win32API under MinGW — Luis Lavena <redmine@...>
Bug #1127: error while compiling Win32API under MinGW
[#21904] 1.9 one-byte trace instruction and trap-instruction replacement? — Rocky Bernstein <rocky.bernstein@...>
Now that Ruby 1.9.1 has been released, if I recall correctly a
[#21937] [Bug #1131] String#unpack("V") does not work correctly is linux on s390x — Ittay Dror <redmine@...>
Bug #1131: String#unpack("V") does not work correctly is linux on s390x
Issue #1131 has been updated by Marcus R端ckert.
[#21944] [Bug #1134] [PATCH] Update racc runtime and fix warnings — Aaron Patterson <redmine@...>
Bug #1134: [PATCH] Update racc runtime and fix warnings
[#21946] New hash : syntax for the 1.8 series? — Brent Roman <brent@...>
At Tue, 10 Feb 2009 16:30:55 +0900,
Hi --
David A. Black wrote:
At Tue, 10 Feb 2009 22:32:19 +0900,
Hi,
On Wed, Feb 11, 2009 at 9:55 AM, Yukihiro Matsumoto <matz@ruby-lang.org> wr=
2009/2/11 Rados=B3aw Bu=B3at <radek.bulat@gmail.com>:
2009/2/11 Pit Capitain <pit.capitain@gmail.com>:
[#21958] ruby 1.9.1 parallel make race — Andrew Walrond <andrew@...>
Hello list,
[#21997] 1.8.7 Specifics — John Barnette <jbarnette@...>
There's a fair amount of talk lately about release management and
On Wednesday 11 of February 2009 19:42:37 John Barnette wrote:
At Mon, 23 Feb 2009 02:48:51 +0900,
On Wed, Feb 11, 2009 at 1:42 PM, John Barnette <jbarnette@gmail.com> wrote:
On Thu, Feb 12, 2009 at 04:01:58AM +0900, Gregory Brown wrote:
On Wed, Feb 11, 2009 at 6:28 PM, Aaron Patterson
Gregory Brown wrote:
On Wed, Feb 11, 2009 at 4:42 PM, John Barnette <jbarnette@gmail.com> wrote:
Luis Lavena wrote:
On Wed, Feb 11, 2009 at 5:55 PM, Charles Oliver Nutter
2009/2/11 Luis Lavena <luislavena@gmail.com>:
Hi,
Hi,
Hello Ezra,
Let me leave a memo to remember issues I can think of.
Urabe Shyouhei wrote:
Charles Oliver Nutter wrote:
Excerpts from Headius: Charles Oliver Nutter's message of Sat Feb 14 00:53:17 +0200 2009:
Brent Roman wrote:
Eero Saynatkari wrote:
Excerpts from Headius: Charles Oliver Nutter's message of Sat Feb 14 20:49:52 +0200 2009:
Charles Oliver Nutter wrote:
Ezra Zygmuntowicz wrote:
Hi,
Brent Roman wrote:
Brent Roman wrote:
Charles Oliver Nutter wrote:
Hongli Lai wrote:
On 11/02/2009, Yukihiro Matsumoto <matz@ruby-lang.org> wrote:
All,
On 12/02/2009, John Barnette <jbarnette@gmail.com> wrote:
[#22040] [Bug #1151] Aliased methods change super logic when retrieved with Object#method — Charles Nutter <redmine@...>
Bug #1151: Aliased methods change super logic when retrieved with Object#method
[#22058] [Bug #1157] missing zlib.rb? — Fred Obermann <redmine@...>
Bug #1157: missing zlib.rb?
[#22065] Dir.glob and duplicates? — Charles Oliver Nutter <charles.nutter@...>
I was fixing a JRuby Dir.glob spec failure where we produced a duplicate
Hi,
Nobuyoshi Nakada wrote:
Ryan Davis wrote:
In article <4996749D.7050009@sun.com>,
Tanaka Akira wrote:
In article <49967AFC.4040006@sun.com>,
Tanaka Akira wrote:
In article <49967EC7.6080105@sun.com>,
Tanaka Akira wrote:
In article <49971135.3020009@sun.com>,
Tanaka Akira wrote:
[#22116] [Bug #1162] Build Assertion Failure with VC+++ - Incorrect flushing of stdout/stderr — Charlie Savage <redmine@...>
Bug #1162: Build Assertion Failure with VC+++ - Incorrect flushing of stdout/stderr
[#22136] Confused about some code in mathn.rb — Charles Oliver Nutter <charles.nutter@...>
In 1.8.6 and 1.8.7, these lines appear at line 202 in mathn.rb:
[#22142] [Patch 191p0 ] for ostruct freeze behavior — Robert Dober <robert.dober@...>
Please find attached a patch for ostruct to behave frozen for already
Robert Dober wrote:
On Sun, Feb 15, 2009 at 8:15 PM, Joel VanderWerf
On Sun, Feb 15, 2009 at 9:30 PM, Robert Dober <robert.dober@gmail.com> wrote:
Do I have to file a bug report?
[#22184] [Bug #1164] 1.9/windows memroy leak with rand() AND inspect — "regis d'aubarede" <redmine@...>
Bug #1164: 1.9/windows memroy leak with rand() AND inspect
[#22206] ruby-1.9.1-p0 build failure on i586 — "Jeroen van Meeuwen (Fedora Project)" <kanarip@...>
Hi there,
> However, I get a i586 build failure:
Roger Pack wrote:
[#22246] YASNP (Yet Another Selector Namespace Proposal) — Yehuda Katz <wycats@...>
The idea is to make selectors like optional versions of Python imports.
Yehuda Katz wrote:
Charles Oliver Nutter wrote:
2009/2/19 Florian Gilcher <flo@andersground.net>
Ok, based on a bunch of comments I got from Aaron Patterson and John
On Feb 20, 2009, at 8:39 AM, Yehuda Katz wrote:
On Sun, Feb 22, 2009 at 04:34:18AM +0900, Jim Weirich wrote:
Excerpts from Aaron Patterson's message of Sun Feb 22 04:35:41 +0200 2009:
=20
Can you explain *why* you don't like it?
Excerpts from Yehuda Katz's message of Mon Feb 23 18:08:29 +0200 2009:
Hi,
Yukihiro Matsumoto wrote:
On Feb 24, 2:07=A0am, Yukihiro Matsumoto <m...@ruby-lang.org> wrote:
Excerpts from brixen's message of Wed Feb 25 00:04:34 +0200 2009:
2009/2/24 Eero Saynatkari <ruby-ml@kittensoft.org>
On Feb 24, 3:17=A0pm, Yehuda Katz <wyc...@gmail.com> wrote:
2009/2/24 Brian Ford <brixen@gmail.com>
I agree that this will be used in ways other than just framework creators. =
I'm also in favor of discussing this, but all I hear so far in opposition is
Florian Gilcher wrote:
On Feb 24, 9:17=A0pm, Yehuda Katz <wyc...@gmail.com> wrote:
On Wed, Feb 25, 2009 at 9:23 AM, Brian Ford <brixen@gmail.com> wrote:
Yehuda, I wonder on one thing. If you want in your framework/library
I thought I'd sent this before...hopefully it's still relevant.
Yehuda Katz wrote:
Yehuda Katz wrote:
Hi,
Yukihiro Matsumoto wrote:
Ola Bini wrote:
Charles Oliver Nutter wrote:
Ola Bini wrote:
2009/2/25 Gary Wright <gwtmp01@mac.com>
On Feb 25, 2009, at 6:45 PM, Yehuda Katz wrote:
Jim Weirich wrote:
Jim Weirich wrote:
[#22269] [Bug #1181] [BUG] thread_free: keeping_mutexes must be NULL — Chris Schlaeger <redmine@...>
Bug #1181: [BUG] thread_free: keeping_mutexes must be NULL
[#22286] [Backport #1183] Adding support for the new hash literal syntax — Akinori MUSHA <redmine@...>
Backport #1183: Adding support for the new hash literal syntax
Hi,
[#22325] suggestions for float — Roger Pack <rogerdpack@...>
Floating point rounding errors are common and "annoying"
On Sat, Feb 21, 2009 at 11:59 PM, Roger Pack <rogerdpack@gmail.com> wrote:
Hi,
Excerpts from Yukihiro Matsumoto's message of Mon Mar 02 12:46:27 +0200 2009:
Excerpts from Kurt Stephens's message of Mon Mar 02 20:27:09 +0200 2009:
>> There is public-domain C code that formats floating-point values as the
> A variant of the float to string conversion that tries to preserve all th=
Brent Roman wrote:
[#22333] [Feature #1193] Justified Error Messages — Simon Chiang <redmine@...>
Feature #1193: Justified Error Messages
[#22336] Floats are freezeable and taintable? — Charles Oliver Nutter <charles.nutter@...>
In adding an optimization for Float I realized that Float objects are
Yes, that would be desirable, if there's not a good reason they aren't
At 09:19 09/02/23, Charles Oliver Nutter wrote:
Hi,
[#22347] On the consideration of macros — "James M. Lawrence" <quixoticsycophant@...>
In a previous thread Charles Oliver Nutter had suggested the removal
[#22353] [Bug #1195] String#% does not include prefix before zero value for # versions of numeric formats — Charles Nutter <redmine@...>
Bug #1195: String#% does not include prefix before zero value for # versions of numeric formats
In article <49a25ec0ce233_84c7e8c1f8909a@redmine.ruby-lang.org>,
Tanaka Akira wrote:
At Tue, 24 Feb 2009 14:16:53 +0900,
Akinori MUSHA wrote:
Hi,
Yukihiro Matsumoto wrote:
[#22365] Surprising behavior in inheritance — Nikolai Weibull <now@...>
Am I the only one surprised by this behavior?
Excerpts from Nikolai Weibull's message of Mon Feb 23 16:53:26 +0200 2009:
[#22383] Proposal: Integer.digit_count — Varun Gupta <thevarungupta@...>
How about having a method to return number of digits in the Integer?
[#22418] [Question]utf-8 data contains BOM - by intention or by accident? — =?ISO-8859-15?Q?Wolfgang_N=E1dasi-Donner?= <ed.odanow@...>
Hi!
I think this has been asked earlier, and I can only repeat it here:
Martin Duerst schrieb:
Hi,
[#22543] [Feature #1218] New method needed to set and get the current recursion limit — Conrad Taylor <redmine@...>
Feature #1218: New method needed to set and get the current recursion limit
Issue #1218 has been updated by Conrad Taylor.
[#22559] [Bug #1219] ostruct freeze still not stable — Robert Dober <redmine@...>
Bug #1219: ostruct freeze still not stable
[#22584] MBARI8 patch fixes bugs caused by incorrect volatile variable declarations — Brent Roman <brent@...>
Hi,
In article <49a9024b.0e0d6e0a.11f5.ffffee2f@mx.google.com>,
I am having an issue with the MBARI patches. In our app the test suite has a
a back trace and ruby -v would be nice.
by back trace do you mean the output of
gdb -core core
[#22597] [Bug #1227] [BUG] object allocation during garbage collection phase — Chris Schlaeger <redmine@...>
Bug #1227: [BUG] object allocation during garbage collection phase
[ruby-core:22130] A message from the maintainer of the 1.8.7+ series
Hi, As I don't feel like sounding very constructive or informative by simply responding to the critisisms and concerns we are facing, I think I need to send a clear message to express my intentions. So allow me to post it as follows. Library developers, If you are looking ahead and come to have a strong will to move to 1.9, don't hesitate and never look too far behind. 1.9 is the only future and 1.8.6 or prior is the ancient past for you. 1.8.7 is the past too, but you might as well support ruby 1.8.7+ as an extra gift for not-ready-to-move users only if you feel it's not too hard. In ruby 1.8.8, syntactic compatibility will be added to make it even easier to write code for both 1.9 and 1.8.8+ in a single source file without compromising optimizations for 1.9. If you still need to write code for 1.8.6 but have some intention to support 1.9 in future, then try running your program under ruby 1.8.7 and the forthcoming ruby 1.8.8 with a warning option (-w) as a start. Your code will mostly run on 1.8.7+ because it has been and will be kept backward compatible with 1.8.6 to a high extent (much more than is thought!) except some rare/unfortunate cases that are fully documented in the NEWS file bundled with 1.8.7. Since 1.8.7 is essentially 1.8.6 plus backports from 1.9, it is almost certain that your code will not run on 1.9 if it doesn't even on 1.8.7. One more good thing about running your code on a more recent 1.8 is that you can see what would stop working on 1.9 because many compatibility warnings have been added since 1.8.6. Try the ruby_1_8 head if you want more. 1.8.6 will keep being continuously supported by a decent maintainer group, which I am thankful from the heart. We will not drop 1.8.6 or 1.8.7+ any soon, but keep in mind that ruby 1.9 is the future. Please consider adding support for 1.9 to your code. I, as the maintainer of the 1.8.7+ series, hope 1.8.7+ could be used as a support tool to help you on your way. Regards, -- Akinori MUSHA / http://akinori.org/