[#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: "Sean E. Russell" <ser@...>
Date: 2004-02-11 20:36:18 UTC
List: ruby-core #2368
On Wednesday 11 February 2004 14:36, Dave Thomas wrote:
> I'd like to propose two more criteria.
>
> 1. Nothing new gets added without complete documentation

This is interesting.  Where, in CVS, should the non-sourcecode documentation 
go?  Are we encouraged to start making directories in ruby/doc?  For that 
matter, where's the official location for unit tests and all the extra bits 
of a project?

In the short time that I've been maintaining REXML in the Ruby tree, I've 
found it rather difficult to maintain because I'm maintaining two distinct 
source trees.  It is unlikely that I'll ever use the Ruby CVS as my primary 
source repository, but it would help if I had the entire REXML tree in there 
somewhere, so that I could easily run tests.

> 2. For every library that gets added, another existing library should
> be removed (using deprecation initially, but actually removed
> eventually).

What happens when some new functionality gets added?  IE, what do you 
deprecate when LDAP support is added to the library set?

-- 
### SER   
### Deutsch|Esperanto|Francaise|Linux|XML|Java|Ruby|Aikido
### http://www.germane-software.com/~ser  jabber.com:ser  ICQ:83578737 
### GPG: http://www.germane-software.com/~ser/Security/ser_public.gpg

In This Thread