[#2367] Standard libraries — Dave Thomas <dave@...>

From ruby-dev summary:

60 messages 2004/02/11

[#2397] PATCH: deprecate cgi-lib, getopts, importenv, parsearg from standard library — Gavin Sinclair <gsinclair@...>

Index: cgi-lib.rb

15 messages 2004/02/12

[#2465] PATCH: OpenStruct#initialize to yield self — Gavin Sinclair <gsinclair@...>

This is a common approach I use to object initialization; I don't know

24 messages 2004/02/19

Re: Standard libraries

From: "NAKAMURA, Hiroshi" <nahi@...>
Date: 2004-02-12 08:19:25 UTC
List: ruby-core #2391
Hi,

> From: "Gavin Sinclair" <gsinclair@soyabean.com.au>
> Sent: Thursday, February 12, 2004 2:16 PM

> in time for 1.8.  My question is: how is a user supposed to know what is
> in "standard library" and what is not.  And why should they care?

To know which library has Ruby quality.  "The Ruby Way" and
consistency are important appeal point of Ruby.  Some library
is just bundled not under Ruby communities review for user's
convenience, at least for now.

Another way: define "standardize" process and import new libs
afrer passing the process.  Though I don't think it works.

Regards,
// NaHi

In This Thread