[#24105] [Bug #1711] Marshal Failing to Round-Trip Certain Recurisve Data Structures — Run Paint Run Run <redmine@...>

Bug #1711: Marshal Failing to Round-Trip Certain Recurisve Data Structures

9 messages 2009/07/01

[#24116] [Bug #1715] Numeric#arg for NaN is Inconsistent Across Versions — Run Paint Run Run <redmine@...>

Bug #1715: Numeric#arg for NaN is Inconsistent Across Versions

10 messages 2009/07/02

[#24240] [Bug #1755] IO#reopen Doesn't Fully Associate with Given Stream on 1.9; Ignores pos on 1.8 — Run Paint Run Run <redmine@...>

Bug #1755: IO#reopen Doesn't Fully Associate with Given Stream on 1.9; Ignores pos on 1.8

8 messages 2009/07/09

[#24321] [Bug #1773] Gem path doesn't honor user gem? — Lin Jen-Shin <redmine@...>

Bug #1773: Gem path doesn't honor user gem?

12 messages 2009/07/14

[#24390] [Feature #1784] More encoding (Big5 series) support? — Lin Jen-Shin <redmine@...>

Feature #1784: More encoding (Big5 series) support?

12 messages 2009/07/16

[#24467] Re: [ruby-cvs:31226] Ruby:r24008 (ruby_1_8_6): Removed private on to_date and to_datetime. — Urabe Shyouhei <shyouhei@...>

Hello.

10 messages 2009/07/21

[#24472] [Feature #1800] rubygems can replace system executable files — Kazuhiro NISHIYAMA <redmine@...>

Feature #1800: rubygems can replace system executable files

13 messages 2009/07/21

[#24530] [Feature #1811] Default BasicSocket.do_not_reverse_lookup to true — Roger Pack <redmine@...>

Feature #1811: Default BasicSocket.do_not_reverse_lookup to true

9 messages 2009/07/23

[#24624] [Bug #1844] Immediates Should Not Respond to :dup — Run Paint Run Run <redmine@...>

Bug #1844: Immediates Should Not Respond to :dup

15 messages 2009/07/30

[ruby-core:24556] Re: request: backport unique requires to 1.8.x

From: Michael Fellinger <m.fellinger@...>
Date: 2009-07-24 17:50:09 UTC
List: ruby-core #24556
On Sat, Jul 25, 2009 at 2:34 AM, Luis Lavena<luislavena@gmail.com> wrote:
> On Fri, Jul 24, 2009 at 10:56 AM, Kirk Haines<wyhaines@gmail.com> wrote:
>> On Fri, Jul 24, 2009 at 5:50 AM, Yehuda Katz<wycats@gmail.com> wrote:
>>> I'd like to see all require features backported (including require_rela=
tive)
>>> and the new behavior that eliminates the possibility of the same paths
>>> described differently being treated differently.
>>
>> For the record, I'm open to this. =C2=A0It seems to be a very beneficial
>> set of functionality to backport.
>>
>
> Me too, I would love to get over the workaround of requiring Pathname
> (which do not work right now Windows) to do requires with full
> pathnames and avoid double requires.
>
> +1 for me.

A workaround is:

require File.expand_path('../relative/path/to/target', __FILE__)

>
> --
> Luis Lavena
> AREA 17
> -
> Perfection in design is achieved not when there is nothing more to add,
> but rather when there is nothing more to take away.
> Antoine de Saint-Exup=C3=A9ry
>
>

--=20
^ manveru

In This Thread