Xref: utzoo comp.object:3308 comp.lang.misc:7585 comp.lang.eiffel:1531
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!uwm.edu!bionet!agate!stanford.edu!leland.Stanford.EDU!elaine35.Stanford.EDU!craig
From: craig@elaine35.Stanford.EDU (Craig Chambers)
Newsgroups: comp.object,comp.lang.misc,comp.lang.eiffel
Subject: Re: A Hard Problem for Static Type Systems
Message-ID: <1991Apr23.195746.6192@leland.Stanford.EDU>
Date: 23 Apr 91 19:57:46 GMT
References: <1991Apr20.010347.28984@leland.Stanford.EDU> <1991Apr23.152110.6500@eua.ericsson.se>
Sender: news@leland.Stanford.EDU (Mr News)
Organization: Stanford University
Lines: 13

In article <1991Apr23.152110.6500@eua.ericsson.se> euaabt@eua.ericsson.se (Anders.Bjornerstedt) writes:
>I suspect that you could express this, or something very close to it, in 
>the language CLU. The problem is I dont have the relevant references 
>accessible, I am short of time, I am lazy, etc etc. So why do I write
>this ? Well to encourage any person out there knowlegable in CLU to try!

I used to work with the CLU people and have written a number of CLU
programs while a student at MIT.  CLU's where clauses provide some of
the solution (they act like the type patterns I alluded to in an
earlier message), but CLU has no subtyping, so it can't handle
comparing subtypes of number.

-- Craig Chambers