41 lines
1.5 KiB
Plaintext
41 lines
1.5 KiB
Plaintext
From: wtanksle at dolphin.openprojects.net (William Tanksley)
|
|
Date: Fri, 30 Apr 1999 17:27:35 GMT
|
|
Subject: Using Python for Modular Artificial Intelligence code
|
|
References: <newscache$bu0saf$a8n$1@news.tne.net.au> <7g94lp$mdu$1@news.worldonline.nl> <newscache$ck80bf$rc4$1@news.tne.net.au>
|
|
Message-ID: <slrn7ijq07.1df.wtanksle@dolphin.openprojects.net>
|
|
Content-Length: 1146
|
|
X-UID: 1392
|
|
|
|
On Fri, 30 Apr 1999 23:07:45 +0930, Tim Auld wrote:
|
|
|
|
>>>I've started looking into Python as the AI scripting language for this
|
|
>>>purpose, but I'm having trouble seeing exactly how I could do this. I
|
|
|
|
>>Where do you use C++ for anyway? GUI's? Build them in Python, forget C++
|
|
>>until you are done and than use C++ to speed up critical sections
|
|
|
|
>system further. The reason I'm using C++ is mainly because I'm familiar
|
|
>with it, and because of speed. I'm aware that Python is relatively slow, so
|
|
>I would rather use C++ as a base from the start, and save myself the trouble
|
|
>of rewriting it all later.
|
|
|
|
If you write everything in Python, you will wind up with a program which
|
|
works far sooner than if you'd written it in C++ (unless you're _REALLY_
|
|
good at C++). You can then pull out the parts which need speedup into C
|
|
or C++.
|
|
|
|
It won't be that much trouble to rewrite -- it seldom is, really. The
|
|
hard part is getting the design, not writing the program. Python offers
|
|
the ideal design language, because it's executable.
|
|
|
|
>Tim
|
|
|
|
--
|
|
-William "Billy" Tanksley
|
|
"But you shall not escape my iambics."
|
|
-- Gaius Valerius Catullus
|
|
|
|
|
|
|
|
|