From: shibata.hiroshi@...
Date: 2015-02-26T00:30:46+00:00
Subject: [ruby-core:68313] [Ruby trunk - Bug #10876] Win32API.new fails when an Array is given for the import argument

Issue #10876 has been updated by Hiroshi SHIBATA.

Backport changed from 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN to 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: REQUIRED

----------------------------------------
Bug #10876: Win32API.new fails when an Array is given for the import argument
https://bugs.ruby-lang.org/issues/10876#change-51668

* Author: Aaron Stone
* Status: Closed
* Priority: Normal
* Assignee: Usaku NAKAMURA
* ruby -v: 2.2.0
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: REQUIRED
----------------------------------------
In Ruby 2.2.0, the Win32API.new method fails when an Array is given for the import argument. In all previous versions, it can be either an Array or a String.

The mistake occurred when Aaron Patterson converted to Fiddle and expected the argument would be an Array ("import.map"), then later Nakamura-san switched to expect a String ("import.chars.map") however both of these are incorrect. The code a few lines above does this: [import].join... so it explicitly allows Array or String.

Links to code history and a patch are offered at https://github.com/ruby/ruby/pull/835



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