From: "Berger, Daniel" <djberge@...>
Date: 2003-01-25T03:59:22+09:00
Subject: Re: Can we attack the 'not enough libraries' thing straight on?



> -----Original Message-----
> From: Daniel P. Zepeda [mailto:daniel@zepeda-zone.net] 
<snip> 
> In the not-a-big-deal category:
> 
> User::grent
> User::pwent -- Password a group utilities. Admittedly, not a 
> big deal

I'm not sure what you mean here.  Are you referring to stuff in the 'etc'
module?
 
>                searched for 'password'
> Proc::killall - kills off a process by name, searched for 
> 'process' and 'killall'

# Equivalent
require "sys-proctable"
Sys::ProcTable.ps{ |p| kill if p.ppid == 2122 }

This  module came up first in a search for "process" on the RAA, btw.  The
name was derived from Dan Urist's Proc::ProcessTable Perl module.

> I find it telling that the OP asked for what pieces were 
> missing, but the 
> discussion tended to naming conventions and module 
> management. There *is* a ton of stuff on CPAN, but a lot of 
> it is not needed, because Ruby obviates the need for it, and 
> of course, my list is not exhaustive, just my experiences. 
> Maybe after all the discussion is done, we'll find that CPAN 
> is huge because it has to be, to add stuff to Perl that Ruby 
> already has, and that the small size of Ruby doesn't show the 
> lack of available functionality, but the power of the core Ruby. 

I agree with you here.  Note the hoard of "Class::" modules that Ruby simply
doesn't need, for example.

Regards,

Dan