[#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: Alexander Kellett <ruby-lists@...>
Date: 2004-02-13 14:16:37 UTC
List: ruby-core #2436
On Friday 13 February 2004 07:00, NAKAMURA, Hiroshi wrote:
> Sorry, I found wrong DESCRIPTION.  Convert to string?
> It returns an Array of cell.data.  Source means everything.

nod.

how about automated tracing (via a new test 
casewrapper which uses the trace functionality)
of test cases which produce prototype listings
(including names [not sure if this is possible to get?], 
 and types of input variables) for each function in 
the public api? something i've been planning to do 
for a long time but never gotten around to.

in fact. why not place documentation in the
test cases?, where it should really be. makes
no sense to clutter the code (unreadable code
is unreadable code, adding comments means
you have duplicated unreadable code, kind
of pointless in my eyes)

both the documentation and the test cases
rely on the runtime api anyway so if the testcases
break - the documentation should be updated.

Alex

In This Thread