[EMAIL PROTECTED] wrote: >> that's just the old "C++/Java is better than Smalltalk/Python/Ruby" >> crap. we've seen it before, and it's no more true when it comes from >> you than when it comes from some Java head. people who've actually used >> dynamic typing knows that it doesn't mean that all objects have random >> types all the time. > > No, it isn't the same old crap. When I define an Access field as > Double, I cannot insert a value such as ">200" or "ND" or "Yes". > I'm not saying static typing is better, just that migrating a dynamic > types to static types may cause difficulties that wouldn't be present > if it was static to static.
dynamic typing != random typing. if your program is using the DB-API to add data to an SQLite database, who, exactly, is inserting the values? who's producing the data? under what circumstances would that code produce or insert arbitrarily typed data? </F> -- http://mail.python.org/mailman/listinfo/python-list
