[ruby-talk:04360] Re: DRY and embedded docs.

Your premises are correct, but I disagree with your
conclusions... :)

When a usage message is printed, efficiency matters
very little. Milliseconds are insignificant when the user
is expected to spend several seconds visually scanning
the output...

Of course, it might be considered a little inelegant. There
might still be A Better Way...

Hal

----- Original Message ----- 
From: Toshiro Kuwabara <[e-mail]>
To: ruby-talk ML <[e-mail]>
Sent: Tuesday, August 08, 2000 10:03 AM
Subject: [ruby-talk:04354] Re: DRY and embedded docs.


> Hi,
> 
> In message "[ruby-talk:04353] Re: DRY and embedded docs."
>     on 00/08/08, Dave Thomas <[e-mail]> writes:
> >I think the latter would be nice. Perhaps it should look for an entry
> >such as
> >
> >  = Usage
> >
> >and just format that. That way, you could just output the usage
> >section of a larger RD document.
> >
> >
> >What do people think?
> 
> Printing Usage message is one of user interface, so a program
> should print it as quickly as possible, but RDtool way of 
> parsing RD is highly costed, maybe.
> 
> RD seems plain text. so, when you want instant plain text output
> which dosn't need to parse RD exactly (ex: printing Usage message),
> there is a way to format RD into plain text with much lower cost
> than RDtool's, maybe.
> 
> ---
> Tosh
> Toshiro Kuwabara
> 
>