From: ser@... (Sean Russell) Date: 2004-05-22T04:48:48+09:00 Subject: Re: How to duck type? - the psychology of static typing in Ruby John Carter wrote in message news:... > I immediately see two problems with implementation though... > > a) Ruby is too dynamic, the value it is called with may well gain the > method between compilation and execution of that line. A case in > point is the 'cgi' module which won't just break under your ruling, it will > shatter. I'll have to take a look at the internals of CGI, but I agree that inferrence typing won't catch everything, and will generate some false warnings. I argue, however, that these cases are more the exception than the rule, and that this makes inferrence typing in Ruby useful. > b) Ruby has a remarkbly "narrow" (local) view of the world as it > compiles, to implement your suggest it would require a more global > view, if not multiple passes. This "local" view is important, it > keeps Ruby simple and fast. Which is why I keep saying, over, and over, and over, that I want inferrence typing to be tied to the use of "-c", not to the execution of the code. How is your postfix project coming along? --- SER