Path: utzoo!mnetor!uunet!husc6!bloom-beacon!athena.mit.edu!peter
From: peter@athena.mit.edu (Peter J Desnoyers)
Newsgroups: comp.lang.misc
Subject: Re: From Modula to Oberon (Really data abstraction in C)
Message-ID: <4042@bloom-beacon.MIT.EDU>
Date: 25 Mar 88 19:08:10 GMT
References: <2827@enea.se> <1557@pasteur.Berkeley.Edu> <3764@bloom-beacon.MIT.EDU> <1217@PT.CS.CMU.EDU> <1220@PT.CS.CMU.EDU>
Sender: daemon@bloom-beacon.MIT.EDU
Reply-To: peter@athena.mit.edu (Peter J Desnoyers)
Organization: Massachusetts Institute of Technology
Lines: 17
Keywords: clu, debuggers

In article <1220@PT.CS.CMU.EDU> edw@IUS1.CS.CMU.EDU (Eddie Wyatt) writes:
> > 
> > [I must admit to some bias here, I feel much more productive using CLU
> > than C.  Other than interoperability with certain existing code, I can't
> > see any reason to use C when CLU is available.]
>
>  Try code speed, progaming tools, debugger ....  
                                    ^^^^^^^^
Not to be rude, but the CLU debugger I used in Guttag & Liskov's
course was much better than C debuggers I've seen - dbx, apollo debug
- among other things the interface was (almost?) a full interpreted
CLU and it supported dynamic linking. Have you used CLU before?  
>--
>Eddie Wyatt e-mail: edw@ius1.cs.cmu.edu

				Peter Desnoyers
				peter@athena.mit.edu