1 Jun 2007 02:06
Re: investigating whether wesnoth is suitable for my AI thesis
John McNabb <mcn4bb <at> gmail.com>
2007-06-01 00:06:13 GMT
2007-06-01 00:06:13 GMT
Welcome to wesnoth. I am not much of a python person, so I will let those who are more closely involved with the python bindings answer those questions. I have, however, been working on a new C++ AI that will add a lot of flexibility via WML, and I have been thinking about some of the issues you have raised involving running the AI from the command line and training it, so I will try and answer those as best I can.. > * I have to figure out some practical stuff and I'm hoping you guys can > help me shed some light on them. we will certainly try... > I read a little bit about restricting python. I do like > reviewing/renaming solutions but personally I don't like technical > restrictions. Python being powerful/versatile makes it a nice language > for doing research with (you can hook into all kinds of existing stuff, > you can quickly prototype something). IMHO you probably can't restrict > any c++ AI so IMHO considering restricting python AI's but not c++ AI's > seems inconsistent. Also it's not like there are lots of python AI's > available for wesnoth so the reviewing/renaming solution probably > doesn't add much to the workload of the volunteers who do this. The difference between the C++ AI and the python AI is that the C++ is essentially restricted at compile time. If the program is well behaved when it is distributed, there is no particular problem. Since the python AI is interpreted, however, it is conceivable that someone could execute malicious code unwittingly. Ok, so the individual would have had to have downloaded the campaign/whatever that had the(Continue reading)
RSS Feed