home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!wupost!uwm.edu!ogicse!mintaka.lcs.mit.edu!ai-lab!life.ai.mit.edu!tmb
- From: tmb@arolla.idiap.ch (Thomas M. Breuel)
- Newsgroups: comp.lang.c++
- Subject: Re: Give me safe C++
- Message-ID: <TMB.92Dec22175118@arolla.idiap.ch>
- Date: 23 Dec 92 01:51:18 GMT
- Article-I.D.: arolla.TMB.92Dec22175118
- References: <1992Dec3.193006.5520@almserv.uucp> <1992Dec6.131757.7448@ucc.su.OZ.AU>
- <716@ulogic.UUCP> <1992Dec20.010907.10429@ucc.su.OZ.AU>
- Reply-To: tmb@idiap.ch
- Organization: IDIAP (Institut Dalle Molle d'Intelligence Artificielle
- Perceptive)
- Lines: 15
- NNTP-Posting-Host: arolla.idiap.ch
- In-reply-to: maxtal@extro.ucc.su.OZ.AU's message of 20 Dec 92 01:09:07 GMT
-
- In article <1992Dec20.010907.10429@ucc.su.OZ.AU> maxtal@extro.ucc.su.OZ.AU (John MAX Skaller) writes:
-
- Have you lost something here? Yes, indeed, rapid
- prototyping is much more difficult when routines in
- parts of the code that never get called must still be
- called with correct parameters.
-
- I don't think this is true. In the greater scheme of things, garbage
- collection, static type checking, an interactive implementation, and
- closures are important for rapid prototyping. Having to "call" "code
- that never gets called" (I assume you are talking about stubs for
- functions that haven't been written yet) with "correct parameters" is
- no problem in my experience.
-
- Thomas.
-