[#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:24107] Re: [ANN] meeting log of RubyDeveloperKaigi20090622

From: Luis Lavena <luislavena@...>
Date: 2009-07-01 18:34:18 UTC
List: ruby-core #24107
On Wed, Jul 1, 2009 at 3:20 PM, Charles Oliver
Nutter<headius@headius.com> wrote:
> 2009/6/23 Yugui (Yuki Sonoda) <yugui@yugui.jp>:
>> =3D=3D=3D If possible
>> I hope to include the following features into the 1.9.2. But they might
>> take too many time for deciding their specs and implementing them.
>> * SQLite as a standard library
>> =A0* [ruby-dev:38463]
>> =A0* assigned to naruse
>
> Ok, an obvious concern here: implementations that can't support native
> extensions will have another new core library they have to support
> somehow. This may mean having to build an FFI version of sqlite
> interface or simply failing to support it. I'm confused why a library
> that works well as a gem (and has newer maintained versions like
> Amalgite) needs to be folded into core. Didn't we want to shrink the
> core set of libraries, rather than grow them?
>

I would have to agree with Charles on this point.

Right now is hard to fix already existing bugs at Ruby for Windows,
adding another extension and keep compatibility with it, provide
binaries during the build process and everything is going to
complicate our existence (RubyInstaller Team).

Also, evolution of code and acceptance of patches to ruby-core takes
times and sometimes got forgotten. We cannot depend on that for every
release of these components.

On the contrary, the gem approach help us update it more often and
deliver alternate versions for Windows users.

--=20
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=E9ry

In This Thread