From ... From: Erik Naggum Subject: Re: Newbie questions [Followup to comp.lang.lisp] Date: 1999/05/07 Message-ID: <3135028813767635@naggum.no>#1/1 X-Deja-AN: 474975301 References: <87btg5pb1y.fsf@2xtreme.net> <372dc20d.11142383@news.select.net> <37326ec5.11965212@news.select.net> <87g15ee8ss.fsf@foobar.orion.no> <372e265f.2137369@news.select.net> <87d80hdy1t.fsf@foobar.orion.no> <372fb91b.39706364@news.select.net> <87aevldw62.fsf@foobar.orion.no> <7gnhjt$p9q$1@nnrp1.dejanews.com> <4ogk0a72c.fsf@beta.franz.com> <37326dd3.5537740@news.select.net> <4KfY2.2160$Xs1.357331@news1.giganews.com> <87emktycnn.fsf@orion.dent.isdn.cs.tu-berlin.de> mail-copies-to: never Organization: Naggum Software; +47 8800 8879; http://www.naggum.no Newsgroups: comp.lang.lisp * Joachim Achtzehnter | In contrast, the Lisp community, if this newsgroup is any indication, | seems to totally discount the value of static typing. that's funny -- I read it exactly that opposite way. Lispers care about typing, including static type information, and because they care, they know what kind of costs are involved in them relative to the benefits and why the C++ model is so fundamentally braindamaged as to become totally unpalatable and useless. _because_ we value static type information, but also know the costs, we have decided against anal-retentive tools, but would use tools that can utilize such information productively. however, the kinds of mistakes that you seem to think are so important do not in fact occur often enough to be a significant problem, so the value would lie in optimization across function calls. this is dangerous territory in an environment where you can change function definitions dynamically. #:Erik