I'll have the duck!

Ruby
101

On Thu, Aug 03, 2006 at 12:49:57AM +0900, Jacob F. wrote:

On 8/2/06, Chad P. [email protected] wrote:

I’d say that duck typing is more a means of allowing you to defer
rigidity until it’s actually beneficial. It has little or nothing to do
with delaying validation, and everything to do with avoiding the
unfortunate circumstance of having to validate before it’s convenient
for your code to have something to validate.

That is one of the most concise statements on the benefits of
duck-typing I’ve ever read. Thanks, Chad!

You’re welcome – and thanks for the compliment.

102

On Tue, Aug 08, 2006 at 09:08:40AM +0900, Jürgen Strobel wrote:

unfortunate circumstance of having to validate before it’s convenient
for your code to have something to validate.

We seem to agree even if you think we don’t.

“avoiding … validation before it’s convenient” vs. “delayed validation”.

“defer rigidity” vs. “dynamic and flexible type validation”

Now where is the difference apart fom wording?

I don’t think we disagree. I just said that’s what I’d say – not that
what you’d say is “wrong”. Mine seemed a little more descriptive.