[#35631] [Ruby 1.9 - Bug #4558][Open] TestSocket#test_closed_read fails after r31230 — Tomoyuki Chikanaga <redmine@...>

23 messages 2011/04/06

[#35632] [Ruby 1.9 - Bug #4559][Open] Proc#== does not match the documented behaviour — Adam Prescott <redmine@...>

13 messages 2011/04/06

[#35637] [Ruby 1.9 - Bug #4561][Open] 1.9.2 requires parentheses around argument of method call in an array, where 1.8.7 did not — Dave Schweisguth <redmine@...>

9 messages 2011/04/07

[#35734] [Ruby 1.9 - Feature #4574][Open] Numeric#within — redmine@...

16 messages 2011/04/13

[#35753] [Ruby 1.9 - Bug #4576][Open] Range#step miss the last value, if end-exclusive and has float number — redmine@...

61 messages 2011/04/14
[#39566] [Ruby 1.9 - Bug #4576] Range#step miss the last value, if end-exclusive and has float number — Marc-Andre Lafortune <ruby-core@...> 2011/09/15

[#39590] [Ruby 1.9 - Bug #4576] Range#step miss the last value, if end-exclusive and has float number — Marc-Andre Lafortune <ruby-core@...> 2011/09/16

[#39593] Re: [Ruby 1.9 - Bug #4576] Range#step miss the last value, if end-exclusive and has float number — Tanaka Akira <akr@...> 2011/09/16

2011/9/17 Marc-Andre Lafortune <[email protected]>:

[#39608] Re: [Ruby 1.9 - Bug #4576] Range#step miss the last value, if end-exclusive and has float number — Masahiro TANAKA <masa16.tanaka@...> 2011/09/17

I have not been watching ruby-core, but let me give a comment for this issu=

[#35765] [Ruby 1.9 - Bug #4579][Open] SecureRandom + OpenSSL may repeat with fork — redmine@...

27 messages 2011/04/15

[#35866] [Ruby 1.9 - Bug #4603][Open] lib/csv.rb: when the :encoding parameter is not provided, the encoding of CSV data is treated as ASCII-8BIT — yu nobuoka <nobuoka@...>

13 messages 2011/04/24

[#35879] [Ruby 1.9 - Bug #4610][Open] Proc#curry behavior is inconsistent with lambdas containing default argument values — Joshua Ballanco <jballanc@...>

11 messages 2011/04/25

[#35883] [Ruby 1.9 - Bug #4611][Open] [BUG] Segementation fault reported — Deryl Doucette <me@...>

15 messages 2011/04/25

[#35895] [Ruby 1.9 - Feature #4614][Open] [RFC/PATCH] thread_pthread.c: lower RUBY_STACK_MIN_LIMIT to 64K — Eric Wong <normalperson@...>

10 messages 2011/04/25

[ruby-core:35855] [Ruby 1.9 - Bug #4597] YAML doesn't consider tab stops as whitespace in mappings

From: Dominik Honnef <dominikh@...>
Date: 2011-04-22 18:36:21 UTC
List: ruby-core #35855
Issue #4597 has been updated by Dominik Honnef.


Okay, I just realized that only the latest YAML specification, 1.2, allows tabs there, while older ones do not. And as far as I know, Ruby's YAML parser doesn't support the 1.2 specification... I guess that makes this bug report invalid :)
----------------------------------------
Bug #4597: YAML doesn't consider tab stops as whitespace in mappings
http://redmine.ruby-lang.org/issues/4597

Author: Dominik Honnef
Status: Open
Priority: Low
Assignee: 
Category: 
Target version: 
ruby -v: ruby 1.9.2p180 (2011-02-18 revision 30909) [x86_64-linux]


The YAML specification states that in a mapping (aka Hash in Ruby), the mapping value indicator (":") has to be separated from the value by white space (see quotation [1]).  The YAML specification also states, that white space is defined as follows: 

 s-space	::=	 #x20 /* SP */	 
 s-tab	::=	 #x9  /* TAB */	 
 s-white	::=	s-space | s-tab

(from http://yaml.org/spec/1.2/spec.html#id2775170)

Based on that, the following two lines of Ruby code should yield the same result:

 YAML.load("foo: bar") # => {"foo"=>"bar"}
 YAML.load("foo:\tbar") # => "foo:\tbar"

As one can see by the annotated results, however, Ruby parses "foo:\tbar" as a scalar and not as a mapping.

The same also happens for inline mappings:

 YAML.load("{ foo: bar }") # => {"foo"=>"bar"}
 YAML.load("{ foo:\tbar }") # => {"foo:\tbar"=>nil} 

That the tabulator is valid for separation is also explicitly stated by http://yaml.org/spec/1.2/spec.html#space/separation/ , which is referenced by quotation 1.


Quotations:
[1]: Normally, YAML insists the “:” mapping value indicator be separated from the value by white space. [from http://yaml.org/spec/1.2/spec.html#: mapping value//]


-- 
http://redmine.ruby-lang.org

In This Thread