Re: C++ sucks for games
From: Christer Ericson (christer_ericson_at_NOTplayTHISstationBIT.sony.com)
Date: 10/28/04
- Next message: Artie Gold: "Re: Question: Program crashs without reaching the breakpoint set at the beginning of main()?"
- Previous message: George Neuner: "Re: C++ sucks for games"
- In reply to: Kenneth Tilton: "Re: C++ sucks for games"
- Next in thread: Gerry Quinn: "Re: C++ sucks for games"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 28 Oct 2004 04:22:11 GMT
In article <ktilton-5B854B.10415227102004@nyctyp02-ge0.rdc-nyc.rr.com>,
ktilton@nyc.rr.com says...
> [...]
> 1. While working I can simply compile a changed (fixed or improved)
> five-line function and re-run. Better, if this is an interactive
> application which pauses for user input, I can do this during a pause,
> then return to the application window and offer new input and see the
> new code run. Or if I land in the debugger because of a bug in some
> function, I can fix the function and then tell the debugger to
> re-execute the stack frame which failed. Where the bug was actually in
> some caller arbitrarily high up the call chain, I can tell the debugger
> to restart /that/ frame.
Indeed, this Lisp concept is so powerful that you'll find
a weak copy of offered for C++ in Visual Studio, namely
the "edit-and-continue" feature. Only Lisp does it better.
Christer Ericson
Sony Computer Entertainment, Santa Monica
- Next message: Artie Gold: "Re: Question: Program crashs without reaching the breakpoint set at the beginning of main()?"
- Previous message: George Neuner: "Re: C++ sucks for games"
- In reply to: Kenneth Tilton: "Re: C++ sucks for games"
- Next in thread: Gerry Quinn: "Re: C++ sucks for games"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
