home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!gatech!rpi!think.com!yale.edu!spool.mu.edu!sgiblab!munnari.oz.au!metro!grivel!metz.une.edu.au!eirvine
- From: eirvine@metz.une.edu.au (Edward Irvine, , ,(Oz) 067 73 2039)
- Newsgroups: sci.engr.mech
- Subject: Re: Any experience with programming in C++ related to Mech.Eng.
- Message-ID: <2450@grivel.une.edu.au>
- Date: 10 Nov 92 10:57:27 GMT
- References: <1992Nov4.131502.10952@uoft02.utoledo.edu>
- Sender: usenet@grivel.une.edu.au
- Reply-To: eirvine@metz.une.edu.au
- Lines: 11
- Originator: eirvine@metz.une.edu.au
-
- From article <1992Nov4.131502.10952@uoft02.utoledo.edu>, by billp@jupiter.cse.utoledo.edu (Bill Parquet):
- > hdorfi@magnus.acs.ohio-state.edu (Hans R Dorfi) writes:
- > : Hi, I am interested in experiences of fellow engineers, who switched to C++.
- > : Basically I have to decide whether to develop the computational part of my
- > : dissertation either in C++ or FORTRAN. I have a basic knowledge of C++ and I am
-
- I think you will find C++ a lot easier to debug than FORTRAN. Beware,
- however, the way C/C++ treats matricies, and the difference between
- declaring a 2D matrix from the stack, and getting memory for it
- from the heap. Confused? "Numerical Recipes in C" has a discussion
- on it.
-