From: "nobu (Nobuyoshi Nakada)" <nobu@...>
Date: 2012-10-25T09:02:03+09:00
Subject: [ruby-core:48213] [ruby-trunk - Bug #7211][Rejected] eval does not respect encoding magic comment


Issue #7211 has been updated by nobu (Nobuyoshi Nakada).

Status changed from Open to Rejected

It fails before eval, but in IRB input.
----------------------------------------
Bug #7211: eval does not respect encoding magic comment
https://bugs.ruby-lang.org/issues/7211#change-31478

Author: vo.x (Vit Ondruch)
Status: Rejected
Priority: Normal
Assignee: 
Category: 
Target version: 
ruby -v: ruby 1.9.3p286 (2012-10-12 revision 37165) [x86_64-linux]


=begin
This should work IMO.

 
 $ LANG=C irb
 irb(main):001:0> eval <<EOF
 irb(main):002:0" # encoding: utf-8
 irb(main):003:0" puts "v��t"
 irb(main):004:0" EOF
 SyntaxError: (irb):3: invalid multibyte char (US-ASCII)
 (irb):1: syntax error, unexpected $end, expecting tSTRING_CONTENT or tSTRING_DBEG or tSTRING_DVAR or tSTRING_END
 	from /usr/bin/irb:12:in `<main>'

I am currently bitten by this behavior in RubyGems. I have .gemspec [1], which have some UTF-8 characters, with the encoding magic comment. While building gem, RubyGems evals the .gemspec code [1], where the magic comment is ignored and build fails:

 $ LANG=C gem build gem-nice-install.gemspec 
 ERROR:  While executing gem ... (ArgumentError)
 invalid byte sequence in US-ASCII



[1] https://gist.github.com/3944821

[2] https://github.com/rubygems/rubygems/blob/master/lib/rubygems/specification.rb#L907
=end



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