From: Christian Boos <cboos@...>
Date: 2001-12-11T02:01:09+09:00
Subject: [ruby-talk:28105] Re: Status of keyword args?

Hello,

I guess I missed the thread about keyword arguments...

Are people really liking the idea?
I think this would add a lot of verbosity. I remember that for another
language (O'Caml -> O'Labl), I found the idea interesting ... until I 
tried it for a while!
It doesn't necessarily make your program more readable, and it quickly
becomes a pain to write this additional info when you obviously know
the meaning of each argument.

At least I would suggest to make this feature optional.
I'm also afraid that it would complexify the C API of Ruby.

Btw. if one wants keyword arguments, what's wrong with the
current way of doing it with a hash?

-- Christian


-----Original Message-----
From: Yukihiro Matsumoto [mailto:matz@ruby-lang.org]
Sent: Monday, December 10, 2001 5:46 PM
To: ruby-talk ML
Subject: [ruby-talk:28102] Re: Status of keyword args?


Hi,

In message "[ruby-talk:28070] Status of keyword args?"
    on 01/12/10, Robert Feldt <feldt@ce.chalmers.se> writes:

|Since there's a rumour 1.8 is coming up soon I wonder if keyword args will
|make it? Guess not since we haven't seen them in 1.7.x.

Unfortunately, no.

|If they aren't gone make it I'd be interested in the reason. Is it simply
|because of no time or is there some fundamental problem with introducing
|them?

Mostly timeframe reason.  It requires heavy rewrite of both API and
implementation.  For example rb_scan_args() works no more with keyword
arguments.

							matz.