Erik de Castro Lopo wrote: > Malcolm V wrote: > > >> The true evil is overloading. Dynamic typing allows operator >>overloading which makes things really hard for anyone to parse correctly.
Whoops, note that in the above allows is overloaded to mean requires (ie: my bad). I didn't mean to imply that the horrors of overloading are only found in the domain of dynamically typed languages, as your example below shows. Also, I don't pull out the wooden stake just for operator overloading, overloading of any kind requires me to think too hard, that's the compiler's job. Of course, for quick off the cuff things, dynamic typing is a god-send and no-one has to think too hard, especially the twit that lets it slip into a production environment. > > Err, sorry, C++ is *not* dynamically typed, but it does allow > operator overloading. My blog entry does have links to definitions > of static and dynamic typing. > > Funnily enough, the C++ standard library is guilty of one of the > most heinous overloading crimes ever, the overloading of the left > and right shift operators for use with streams. Nasty stuff. > > Erik Cheers, Malcolm V. _______________________________________________ coders mailing list coders@slug.org.au http://lists.slug.org.au/listinfo/coders
