[#70252] Re: [ruby-cvs:58640] nobu:r51492 (trunk): node.c: NODE_ALLOCA for ALLOCV — Eric Wong <normalperson@...>
Besides possible backwards compatibility, can we drop volatile
3 messages
2015/08/05
[#70257] [Ruby trunk - Feature #11420] [Open] Introduce ID key table into MRI — ko1@...
Issue #11420 has been reported by Koichi Sasada.
11 messages
2015/08/06
[#70337] Re: [Ruby trunk - Feature #11420] [Open] Introduce ID key table into MRI
— Eric Wong <normalperson@...>
2015/08/11
Nice. Thank you guys for looking into this.
[#70349] Re: [Ruby trunk - Feature #11420] [Open] Introduce ID key table into MRI
— Eric Wong <normalperson@...>
2015/08/12
Btw, did you consider using flexible array to avoid extra malloc
[#70355] Re: [Ruby trunk - Feature #11420] [Open] Introduce ID key table into MRI
— Юрий Соколов <funny.falcon@...>
2015/08/12
I thought to suggest to embed hash_id_table directly into places when it is
[#70356] Re: [Ruby trunk - Feature #11420] [Open] Introduce ID key table into MRI
— SASADA Koichi <ko1@...>
2015/08/12
On 2015/08/13 4:29, Юрий Соколов wrote:
[#70358] Re: [Ruby trunk - Feature #11420] [Open] Introduce ID key table into MRI
— Eric Wong <normalperson@...>
2015/08/12
SASADA Koichi <ko1@atdot.net> wrote:
[#70509] [Ruby trunk - Misc #11276] [RFC] compile.c: convert to use ccan/list — ko1@...
Issue #11276 has been updated by Koichi Sasada.
3 messages
2015/08/21
[#70639] the undefined behavior of an iterator if it is modified inside of the block to which it yields — Daniel Doubrovkine <dblock@...>
(this is my first time e-mailing list list, so apologies for any misstep :)
4 messages
2015/08/31
[ruby-core:70346] [Ruby trunk - Bug #11436] Date parsing probably doesn't match for the longest regular expression
From:
dragan.glumac@...
Date:
2015-08-12 09:59:16 UTC
List:
ruby-core #70346
Issue #11436 has been updated by Dragan Glumac. I've realised that that there are methods on the date like strptime which give me a fine-grained control of the date parsing, so maybe this catch-all parse method is greedy by design. Perhaps it could just be mentioned in the documentation for the parse method as a warning to the unwary (if it hasn't been already). ---------------------------------------- Bug #11436: Date parsing probably doesn't match for the longest regular expression https://bugs.ruby-lang.org/issues/11436#change-53762 * Author: Dragan Glumac * Status: Open * Priority: Normal * Assignee: * ruby -v: * Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN ---------------------------------------- If you parse a string 'Edinburg Fringe' with the Date::parse method, you'll get the date of next Friday in Edinburgh time zone. Some of our tests are failing for this reason. I expect that parse is matching the argument via a regular expression, but it's greedy so perhaps RegEx needs a minor update. In any case, if you wanted to reproduce this defect I've attached the script. Hope that helps Dragan ---Files-------------------------------- edinburgh_fringe.rb (183 Bytes) -- https://bugs.ruby-lang.org/