[#39227] [Ruby 1.9 - Bug #5264][Open] Commit 33157 — Charlie Savage <cfis@...>
[#39241] [Ruby 1.9 - Bug #3422][Closed] Object.const_get(:A, false) can access BasicObject::A — Nobuyoshi Nakada <nobu@...>
On Sat, Sep 3, 2011 at 04:57, Nobuyoshi Nakada <nobu@ruby-lang.org> wrote:
> Why is this issue closed? Is the current behaviour acceptable?
[#39260] RubySpec vs CRuby's test/... — Marc-Andre Lafortune <ruby-core-mailing-list@...>
Before the release of Ruby 1.9.2 it was decided that Ruby releases
Hi,
(09/05/2011 03:54 AM), Marc-Andre Lafortune wrote:
Hi,
2011/9/5 Marc-Andre Lafortune <ruby-core-mailing-list@marc-andre.ca>:
On Mon, Sep 5, 2011 at 3:08 AM, NARUSE, Yui <naruse@airemix.jp> wrote:
2011/9/5 Marc-Andre Lafortune <ruby-core-mailing-list@marc-andre.ca>:
I'll jump in with some context from the JRuby perspective.
2011/9/7 Charles Oliver Nutter <headius@headius.com>:
On Wed, Sep 7, 2011 at 4:17 AM, NARUSE, Yui <naruse@airemix.jp> wrote:
Hi,
Yukihiro Matsumoto:
(2011/09/09 1:29), Michael Klishin wrote:
On Thu, Sep 8, 2011 at 4:19 PM, NARUSE, Yui <naruse@airemix.jp> wrote:
Hello Luis,
On Thu, Sep 8, 2011 at 5:34 PM, Masaya TARUI <tarui@prx.jp> wrote:
On Thu, Sep 8, 2011 at 3:57 PM, Luis Lavena <luislavena@gmail.com> wrote:
On Thu, Sep 8, 2011 at 5:07 PM, Charles Oliver Nutter
(2011/09/08 15:28), Charles Oliver Nutter wrote:
2011/9/9 Charles Oliver Nutter <headius@headius.com>:
On Thu, Sep 8, 2011 at 9:47 PM, NARUSE, Yui <naruse@airemix.jp> wrote:
I realize that I'm a small fish in this ocean, but for every release
(09/09/2011 03:51 PM), Kirk Haines wrote:
[#39267] [Ruby 1.9 - Bug #5273][Open] Float#round returns the wrong floats for higher precision — Marc-Andre Lafortune <ruby-core@...>
[#39279] [Ruby 1.9 - Bug #5276][Assigned] 4294967295.8.round is 4294967295 on 32bit — Yui NARUSE <naruse@...>
[#39304] [Ruby 1.9 - Bug #5285][Open] Ruby 1.9.2 throws exception on sort of array containing true AND false values — Martin Corino <mcorino@...>
[#39309] [Ruby 1.9 - Bug #5287][Open] 1.9.3 - Interpolation in a string causes the string's encoding to be set to ASCII-8BIT — Jon Leighton <j@...>
[#39326] [Ruby 1.9 - Feature #5291][Open] Enabling GC Profiler GC_PROFILE_MORE_DETAIL and CALC_EXACT_MALLOC_SIZE — Charlie Savage <cfis@...>
[#39360] What is the role of rb_objspace_t in gc.c? — Kurt Stephens <ks@...>
What is the role of rb_objectspace_t and the pointers to it inside gc.c?
[#39380] [Ruby 1.9 - Bug #5299][Open] Segmentation fault when using TweetStream gem in ruby 1.9.3 — Dushyanth Maguluru <dushyanth.maguluru@...>
[#39435] [Ruby 1.9 - Bug #5306][Open] Application Hangs Due to Recent rb_thread_select Changes — Charlie Savage <cfis@...>
[#39450] Comments on HowToReportEnglish — Andrew Grimm <andrew.j.grimm@...>
I've done some proofreading for HowToReportEnglish, and I'd like to
Hello,
Hello
[#39451] File.realpath behavior questions — Luis Lavena <luislavena@...>
Hello,
Hi,
On Sun, Sep 11, 2011 at 4:48 AM, Nobuyoshi Nakada <nobu@ruby-lang.org> wrote:
[#39480] Modifications to libraries like Rake should be done upstream first — Luis Lavena <luislavena@...>
Hello,
[#39484] [Ruby 1.9 - Bug #5309][Open] 0.6.to_r != "0.6".to_r — Brian Ford <brixen@...>
[#39487] File::BINARY does not behave as advertised — Cameron Pope <camerooni@...>
Hello -
On Mon, Sep 12, 2011 at 16:00, Cameron Pope <camerooni@gmail.com> wrote:
[#39498] [Ruby 1.9 - Feature #5310][Open] Integral objects — Kenta Murata <muraken@...>
On Mon, Sep 12, 2011 at 6:15 PM, Kenta Murata <muraken@gmail.com> wrote:
[#39539] [Ruby 1.9 - Feature #5321][Open] Introducing Numeric#exact? and Numeric#inexact? — Kenta Murata <muraken@...>
[#39597] File.expand_path ~username always trigger ArgumentError on Windows — Luis Lavena <luislavena@...>
Hello,
[#39618] [Ruby 1.9 - Bug #5335][Open] [RFC/PATCH] test_old_thread_select: timing tweaks — Eric Wong <normalperson@...>
[#39627] Re: [ruby-cvs:40472] drbrain:r33294 (trunk): * test/openssl/test_ssl.rb (class OpenSSL): Test — "NARUSE, Yui" <naruse@...>
(2011/09/19 9:28), drbrain@ruby-lang.org wrote:
On Sep 19, 2011, at 11:33 AM, NARUSE, Yui wrote:
2011/9/19 Eric Hodel <drbrain@segment7.net>:
[#39629] [Ruby 1.9 - Feature #5341][Open] Add SSL session reuse to Net::HTTP — Eric Hodel <drbrain@...7.net>
On 10/26/2011 11:39 AM, Eric Hodel wrote:
[#39632] [Ruby 1.9 - Bug #5342][Open] ConditionVariable can wake a Thread that is no longer waiting on it — Mike Perham <mperham@...>
[#39634] [Ruby 1.9 - Bug #5343][Open] Unexpected blocking behavior when interrupt Socket#accept — Tomoyuki Chikanaga <nagachika00@...>
[#39672] [Ruby 1.9 - Feature #5352][Open] How about using <> to represent Here Document? — Joey Zhou <yimutang@...>
[#39673] [Ruby 1.9 - Bug #5353][Open] TLS v1.0 and less - Attack on CBC mode — Martin Bosslet <Martin.Bosslet@...>
[#39684] [Ruby 1.9 - Bug #5357][Open] Indentation of nested operators should nest — Nikolai Weibull <now@...>
[#39690] [Ruby 1.9 - Feature #5360][Open] BasicObject#binding — Thomas Sawyer <transfire@...>
[#39696] Time spent on expanding load path — Juan Wajnerman <jwajnerman@...>
I've been following the performance of Ruby 1.9.x since the beginning. I work with many quite big Rails projects and as the number of used gems explode, the impact on the loading time for the application has increased very noticeably.
[#39700] [Ruby 1.9 - Feature #5364][Open] How about new syntax: "object.\method" returns a Method instance? — Joey Zhou <yimutang@...>
[#39704] [Ruby 1.9 - Bug #5365][Open] WEBrick lacks the application/javascript and image/svg+xml MIME types. — Hal Brodigan <postmodern.mod3@...>
[#39740] [Ruby 1.9 - Feature #5372][Open] Promote blank? to a core protocol — Alex Young <alex@...>
On Tue, Sep 27, 2011 at 06:18:19PM +0900, Alex Young wrote:
On 27/09/2011 19:46, Aaron Patterson wrote:
On Sep 27, 2011, at 6:52 PM, Alex Young wrote:
Eric Hodel wrote in post #1024462:
Hi,
On 04/10/11 16:52, Nobuyoshi Nakada wrote:
[#39772] ObjectSpace.reference_form(obj) #=> references_array — SASADA Koichi <ko1@...>
Hi,
Hi,
Hi,
(2011/09/30 5:37), hemant wrote:
On 09/30/2011 07:08 AM, SASADA Koichi wrote:
Revisit.
On Sep 20, 2012, at 6:14 PM, SASADA Koichi <ko1@atdot.net> wrote:
(2012/09/25 7:38), Eric Hodel wrote:
I'm sorry for late reply.
(2012/09/25 15:18), Narihiro Nakamura wrote:
[ruby-core:39473] [Ruby 1.9 - Feature #5120] String#split needs to be logical
Issue #5120 has been updated by Alexey Muranov.
Adam Prescott wrote:
>
> str.split("") already gets you the array of "letters" (as does
> str.chars.to_a), but since you feel that str.split("") should raise an
> error or have another return value, do you think str.split("") should
> break existing code which uses split("") to get characters?
>
Thanks for pointing out str.chars.to_a, but i think that it would be more natural to have a single method that would do this.
I understand that this would break existing code, i was discussing the issue not from the point of view of maintaining existing code, but from the point of view of "improving" the language, according what would look like an improvement to me.
As a person new to Ruby, i expressed my "astonishment" at the current behavior of #split, and tried to contribute to POLA.
> What's the reasoning behind str.split("") raising an error? I can't
> see a good reason for it. Equally, I can see no good reason for
> treating "a".split("") the same in return value as "a".split("a"). In
> the latter, there is more to be considered because the receiver itself
> contains "a". Why should "a".split("") return ["", "a", ""]?
I think that #split should treat all strings equally, whether empty or not.
Maybe i've missed something (then please point me to the explanation), but i do not see how the treatment of empty and non-empty strings can be particular cases of a general rule.
What is the general rule, which gives such different results for empty and non-empty strings?
I think that "a".split("") should return ["", "a", ""], because this would be more logical, then when "a".split("",-1) returns ["a", ""], as it does now.
I think that in most other cases #split(str) should behave as #split(str,-1) behaves now, because the decision to discard trailing empty elements seems arbitrary.
By analogy with "a".split(",",-1) currently returning ["",""], i think that:
",".split(",") should return ["",""],
"".split("") should return ["",""] (if not forbidden altogether),
",".split("") should return ["", ",", ""] (if not forbidden).
But, as i said, this is only a suggestion to preserve consistency: use the same general rule to split on empty and non-empty strings.
What is the rule now?
It seems like the #split on the empty string is treated separately, but then it should be a separate method.
The easiest way to be consistent, in my opinion, is to forbid splitting on the empty string and to use a different method for the array of letters.
----------------------------------------
Feature #5120: String#split needs to be logical
http://redmine.ruby-lang.org/issues/5120
Author: Alexey Muranov
Status: Open
Priority: Normal
Assignee:
Category:
Target version:
I would call this a bug, but i am new to Ruby, so i report this as a feature request.
Here are examples showing a surprising and inconsistent behavior of String#split method:
"aa".split('a') # => []
"aab".split('a') # => ["", "", "b"]
"aaa".split('aa') # => ["", "a"]
"aaaa".split('aa') # => []
"aaaaa".split('aa') # => ["", "", "a"]
"".split('') # => []
"a".split('') # => ["a"]
What is the definition of *split*?
In my opinion, there should be given a simple one that would make it clear what to expect.
For example:
str1.split(str2) returns a maximal array of non-empty substrings of str1 which can be concatenated with copies of str2 to form str1.
Additional precisions can be made to this definition to make clear what to expect as the result of "baaab".split("aa").
Thanks for attention.
--
http://redmine.ruby-lang.org