Author: Andreas Guettinger
Date: 19:50:50 11/17/02
Go up one level in this thread
On November 17, 2002 at 19:58:14, Bob Durrett wrote: > >In the Rookie 2 chess engine thesis I'm looking at, the author keeps giving >pseudo-code to illustrate the points in the narrative. > >Why didn't he just give the code? Too much? OK. That much is obvious. > >But how to decide whether or not code is "pseudo"? > >Yes, I know that's a dumb question. But I'm at the beginning. > >Bob D. Normally, the provider of the code should write if it is pseudo-code or not. The point in showing pseudo-code is that you can show an algorithm in a way that people will understand it by writting just the relevant part. This code usually does not compile like it is written. In C you do the definitions of functions and variables not always at the place of the code you want to show, and therefore it would be tiresome to copy and paste all the relevant functions and definitions together. Furthermore, in pseudo code you can give a more comprehensible structure, without being concerned if the code will still compile. Andy
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.