«

On Tue, Aug 08, 2006 at 09:08:40AM +0900, J=FCrgen Strobel wrote:
> On Thu, Aug 03, 2006 at 12:39:38AM +0900, Chad Perrin wrote:
> > On Thu, Aug 03, 2006 at 12:01:50AM +0900, J=FCrgen Strobel wrote:
> > >=20
> > > I repeat: duck typing is not to produce bombing out code, but a new=
*
> > > way to handle dynamic and flexible type validation "late", with the
> > > objective to ease development and produce clean code.
> >=20
> > 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.
>=20
> We seem to agree even if you think we don't.
>=20
> "avoiding ... validation before it's convenient" vs. "delayed validatio=
n".
>=20
> "defer rigidity" vs. "dynamic and flexible type validation"
>=20
> 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.

--=20
CCD CopyWrite Chad Perrin [ http://ccd.apotheon.org ]
"It's just incredible that a trillion-synapse computer could actually
spend Saturday afternoon watching a football game." - Marvin Minsky