Backport #4208: ENV.delete warns even if it succeeded on Windows.

• Status: Rejected
• Assignee: yugui (Yuki Sonoda)

[phasis68 (Heesob Park)]

=begin
C:\work>ruby -ve "ENV['foo']='bar';ENV.delete('foo');p ENV['foo']"
ruby 1.9.2p136 (2010-12-25 revision 30365) [i386-mswin32_90]
-e:1: warning: failed to set environment variable. Ruby 1.9.3 will raise SystemCallError in this case.
nil

This bug is related with http://redmine.ruby-lang.org/issues/show/3825
=end

[usa (Usaku NAKAMURA)]

• Category set to core
• Status changed from Open to Assigned
• Assignee set to yugui (Yuki Sonoda)

=begin
r29225 and r29377 of trunk.
=end

[yugui (Yuki Sonoda)]

• Status changed from Assigned to Feedback

It is not reproducible with (Ruby 1.9.2 HEAD, mswin32_100, Windows 7). Is it still reproducible in your environment?

[phasis68 (Heesob Park)]

It is reproducible on Windows XP.

C:>ver

Microsoft Windows XP [Version 5.1.2600]

C:\Ruby192\bin>ruby -ve "ENV['foo']='bar';ENV.delete('foo')"
ruby 1.9.2p136 (2010-12-25) [i386-mingw32]
-e:1: warning: failed to set environment variable. Ruby 1.9.3 will raise SystemCallError in this case.

[naruse (Yui NARUSE)]

• Status changed from Feedback to Rejected