From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13781 invoked by alias); 8 Nov 2003 11:38:51 -0000 Mailing-List: contact xconq7-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: xconq7-owner@sources.redhat.com Received: (qmail 13768 invoked from network); 8 Nov 2003 11:38:49 -0000 Received: from unknown (HELO smtp14.fre.skanova.net) (195.67.227.31) by sources.redhat.com with SMTP; 8 Nov 2003 11:38:49 -0000 Received: from [212.181.162.155] (h155n1fls24o1048.bredband.comhem.se [212.181.162.155]) by smtp14.fre.skanova.net (8.12.10/8.12.10) with ESMTP id hA8Bce2n029571; Sat, 8 Nov 2003 12:38:46 +0100 (CET) X-Sender: u22611592@m1.226.comhem.se Message-Id: In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 08 Nov 2003 13:06:00 -0000 To: "Brandon J. Van Every" From: Hans Ronne Subject: Re: The gory Xconq kernel Cc: xconq7@sources.redhat.com X-SW-Source: 2003/txt/msg00608.txt.bz2 >I have no interest in rewriting the entire Xconq kernel. That kind of >project is what I call a Complete Waste Of Time. If you can't >incrementally modify it, better to write a new game from scratch! Sure you can incrementally modify it. That's what we do all the time. But it's written in C, like it or not. Did I take your statement about never touching C too literally? >That last sentence is rather disturbing. Are you saying that no matter >what one's skill level, the Xconq kernel is such spaghetti that modules >of it simply cannot be untangled? I can see myself doing Python in >kernel, for bits and pieces here and there, as I think of a feature I >want / need. Particularly for AI stuff. Are you saying this ain't >likely to be feasible in practice? Not at all. All I'm saying it's hard work. You won't do it in a weekend, irrespective of your skill level. That being said, I think the Xconq kernel could benefit from a rewrite in an object oriented language and I encourage any such attempts. But so far they have remained attempts :-/. >Caveat: I have yet to attempt to understand the Xconq source code or >read any docs about it. Getting it to even build on Windoze was the 1st >priority, and I still don't have a working build. I don't understand this problem. As Juergen Ruehle said, it's pretty straightforward to build it under MSVC (or CodeWarrior). Didn't take me many minutes to get a working Windows build, though I am not a Windows developer. All you need in addition to the runtime C stuff are five libraries: tcl84.lib, tk84.lib, kernel32.lib, user32.lib and wsock32.lib. Replace tcl84.lib and tk84.lib with SDL.lib and SDLMain.x86.lib to build the SDL interface. Hans