[#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: "Gavin Sinclair" <gsinclair@...>
Date: 2004-02-11 23:55:34 UTC
List: ruby-core #2374
> Hi,
>
> In message "Standard libraries"
>     on 04/02/12, Dave Thomas <dave@thomases.com> writes:
>
> |I'd like to propose two more criteria.
> |
> |1. Nothing new gets added without complete documentation
> |2. For every library that gets added, another existing library should
> |be removed (using deprecation initially, but actually removed
> |eventually).
> |
> |If we have a problem with Ruby right now, it's that we're bulking up
> |with code that no one knows exists/how to use.
>
> I didn't see any smiley here, how much are you serious?
>
> Here's the modified version of your criteria, that I can accept:
>
>   1. newly added things will be canceled if they are not documented
>      completely before the stable release.
>
>   2. when new library is added, let us start discussion about removing
>      another out-of-date library.
>
> 							matz.

Sounds good.  Is there sense in starting a discussion about removing some
out-of-date libraries now?

Also: base64.  Can we put the recent HEAD change (modularisation, and
deprecating the top-level namespace pollution) in the 1.8 branch as well? 
It makes sense to deprecate it now, IMO.

Cheers,
Gavin



In This Thread