[ruby-talk:04035] Re: Optional argument and *rest simultaneou sly

Aleksi
> |You're releasing 1.6 quite soon? If not, and there will be 
> 1.4.6, shouldn't
> |this be prohibited since it will lead to misbehaving code. 

Matz:
> I think I'm going to release 1.4.6 next week.
> 
> And you ask me to prohibit what?

I was wondering if simultaneous optional arguments and *rest should be
allowed or disabled until they work right. But I guess the job is not worth
of it. It seems that people are not mixing various calling methods, since
I'm the only one reporting about the possible problem. What it comes to me,
I can cope with current implementation - now that I know it's not working.

Part of the deal here is, that I don't know your policies. I don't know
whether you promote that the language should not allow constructs it's not
handling well (this suggests we have to remove optional arguments and *rest
arguments to be valid when used simultaneously) or if you're forgiving and
let people mess their code with syntax which will work in the future, but is
not implemented fully yet. It seems you're supporting the latter, and it's
perfectly ok. It's just good to be known widely.

	- Aleksi