From: Daniel Brockman <daniel@...>
Date: 2005-07-20T02:16:33+09:00
Subject: Re: [RCR] nil for unassigned keys

Hi Eric,

> I thought you were going to submit an RCR for this (not
> too related to the original RCR topic of this thread - nil
> for unassigned keys - of a hash).

I know, I'm sorry.  As I said earlier in this thread,

Myself> That reminds me, I promised I would write an RCR for
Myself> allowing trailing argument after the splatting one.

Myself> It was said that optional arguments should be
Myself> allowed before the splat, but not after it.

Eric, what is your opinion on this?  Do you think these

   def foo(a, b=nil, c, d=nil, e) ... end
   def bar(a, b=nil, *c, d=nil, e) ... end
   def baz(*a, b=nil, c=nil) ... end

should all be allowed?

If so, then which variable, b or c, should be bound when
invoking baz with one argument?  The obvious answer is b,
but you could argue that c makes more sense, since c is
farthest from the splat.

> Here is what was said in the thread "Re: iterators and
> block arguments" (which covers your concern above):

I don't think it quite covers my concern, as it only deals
with the case of mandatory arguments after the splat.

-- 
Daniel Brockman <daniel@brockman.se>

    So really, we all have to ask ourselves:
    Am I waiting for RMS to do this?   --TTN.