this or is it mostly proprietary "trade secret" type affairs? Are most of
the sim programmers using C?
Thanks,
Ben
Thanks,
Ben
Here's a useful resource...
http://www.gameai.com/aimain.html
I think your best bet would be a book search on amazon, I'm pretty sure
there are published books on the subject.
As for the language, I think you'll find the majority of 'sim programmers'
are using C or C++, and the trend is towards C++.
Although generally Prolog is billed as "THE language for AI" ... I
never liked it much myself however.
I got this info from an interview with Ratbag's designers I read when
Powerslide was released. Maybe others have some more info . . . ?
Ryan
*SPLUTTER* It's a wonderful, elegant, eye-opener of a language!!! Only
problems are that it is a little slow for regular applications, and rather
hard to learn, too (hard in terms of adjusting to the paradigm, NOT hard
like C/C++'s walking-on-eggs approach). Most things are done recursively
(like Lisp) and there are added complications in that the control flow is
not exactly explicit in the code listing. The Prolog code to solve the
Towers of Hanoi problem is something like 5 lines long . . .
Sorry for the intensely nerdish rant ;-)
Ryan
> *SPLUTTER* It's a wonderful, elegant, eye-opener of a language!!! Only
> problems are that it is a little slow for regular applications, and rather
> hard to learn, too (hard in terms of adjusting to the paradigm, NOT hard
> like C/C++'s walking-on-eggs approach). Most things are done recursively
> (like Lisp) and there are added complications in that the control flow is
> not exactly explicit in the code listing. The Prolog code to solve the
> Towers of Hanoi problem is something like 5 lines long . . .
> Sorry for the intensely nerdish rant ;-)
The problem that *I* had with Prolog is that I have been a "functional"
(Cobol/Assembly/Pascal/C/C++/Java/C#) programmer for too long by the
time I tried to learn it. I simply could NOT adjust to the paradigm.
FWIW: I had the same problem trying to adjust to LISP. (Lots of
Irritating Stupid Parenthesis)
> > > Although generally Prolog is billed as "THE language for AI" ... I
> > > never liked it much myself however.
> > *SPLUTTER* It's a wonderful, elegant, eye-opener of a language!!! Only
> > problems are that it is a little slow for regular applications, and rather
> > hard to learn, too (hard in terms of adjusting to the paradigm, NOT hard
> > like C/C++'s walking-on-eggs approach). Most things are done recursively
> > (like Lisp) and there are added complications in that the control flow is
> > not exactly explicit in the code listing. The Prolog code to solve the
> > Towers of Hanoi problem is something like 5 lines long . . .
> > Sorry for the intensely nerdish rant ;-)
> You pointed it out perfectly.
> The problem that *I* had with Prolog is that I have been a "functional"
> (Cobol/Assembly/Pascal/C/C++/Java/C#) programmer for too long by the
> time I tried to learn it. I simply could NOT adjust to the paradigm.
> FWIW: I had the same problem trying to adjust to LISP. (Lots of
> Irritating Stupid Parenthesis)
> > > > Although generally Prolog is billed as "THE language for AI" ... I
> > > > never liked it much myself however.
> > > *SPLUTTER* It's a wonderful, elegant, eye-opener of a language!!! Only
> > > problems are that it is a little slow for regular applications, and rather
> > > hard to learn, too (hard in terms of adjusting to the paradigm, NOT hard
> > > like C/C++'s walking-on-eggs approach). Most things are done recursively
> > > (like Lisp) and there are added complications in that the control flow is
> > > not exactly explicit in the code listing. The Prolog code to solve the
> > > Towers of Hanoi problem is something like 5 lines long . . .
> > > Sorry for the intensely nerdish rant ;-)
> > You pointed it out perfectly.
> > The problem that *I* had with Prolog is that I have been a "functional"
> > (Cobol/Assembly/Pascal/C/C++/Java/C#) programmer for too long by the
> > time I tried to learn it. I simply could NOT adjust to the paradigm.
> > FWIW: I had the same problem trying to adjust to LISP. (Lots of
> > Irritating Stupid Parenthesis)
This is my solution in dc (Simple calculator program on unixes)
(The output is which ring, from peg, to peg):
-- cut here
2[SdSsSaln1-dSn0<xLnLaLsLdc]sy1[ldlslalyx12Pldlslnfclslaldlyx]sx3? 1+snlyx
-- cut here
Of course, the five prolog-lines may be a bit more readable...
You're forgiven.:-)
--
[asbjxrn] [lLd25z*%ds1-100/sLlSdI%ds2-O/sSl1l2*PlL0<l]sl
21172310731916131628237117 3237142523312SSSLllxq
> > The Prolog code to solve the Towers of Hanoi problem is something
> > like 5 lines long . . .
> Five lines, huh?
> This is my solution in dc (Simple calculator program on unixes)
> (The output is which ring, from peg, to peg):
> -- cut here
> 2[SdSsSaln1-dSn0<xLnLaLsLdc]sy1[ldlslalyx12Pldlslnfclslaldlyx]sx3? 1+snlyx
> -- cut here
> Of course, the five prolog-lines may be a bit more readable...
> > Sorry for the intensely nerdish rant ;-)
> You're forgiven.:-)
> --
> [asbjxrn] [lLd25z*%ds1-100/sLlSdI%ds2-O/sSl1l2*PlL0<l]sl
> 21172310731916131628237117 3237142523312SSSLllxq
> > The Prolog code to solve the Towers of Hanoi problem is something
> > like 5 lines long . . .
> Five lines, huh?
> This is my solution in dc (Simple calculator program on unixes)
> (The output is which ring, from peg, to peg):
> -- cut here
> 2[SdSsSaln1-dSn0<xLnLaLsLdc]sy1[ldlslalyx12Pldlslnfclslaldlyx]sx3? 1+snlyx
> -- cut here
Gunnar, waiting to see the INTERCAL version.
--
Gunnar
#31 SUCKS#015 Tupperware MC#002 DoD#0x1B DoDRT#003 DoD:CT#4,8 Kibo: 2
DE RECTIS NON TOLERANDUM EST
> > The Prolog code to solve the Towers of Hanoi problem is something
> > like 5 lines long . . .
> Five lines, huh?
> This is my solution in dc (Simple calculator program on unixes)
> (The output is which ring, from peg, to peg):
> -- cut here
> 2[SdSsSaln1-dSn0<xLnLaLsLdc]sy1[ldlslalyx12Pldlslnfclslaldlyx]sx3? 1+snlyx
> -- cut here
Gunnar, waiting for that INTERCAL version.
--
Gunnar
#31 SUCKS#015 Tupperware MC#002 DoD#0x1B DoDRT#003 DoD:CT#4,8 Kibo: 2
DE RECTIS NON TOLERANDUM EST
> > > The Prolog code to solve the Towers of Hanoi problem is something
> > > like 5 lines long . . .
> > Five lines, huh?
> > This is my solution in dc (Simple calculator program on unixes)
> > (The output is which ring, from peg, to peg):
> > -- cut here
> > 2[SdSsSaln1-dSn0<xLnLaLsLdc]sy1[ldlslalyx12Pldlslnfclslaldlyx]sx3? 1+snlyx
> > -- cut here
> cool! a programming contest!
> Gunnar, waiting to see the INTERCAL version.