From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18653 invoked by alias); 8 Nov 2003 03:06:37 -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 18646 invoked from network); 8 Nov 2003 03:06:37 -0000 Received: from unknown (HELO outbound28-2.lax.untd.com) (64.136.28.160) by sources.redhat.com with SMTP; 8 Nov 2003 03:06:37 -0000 Received: (qmail 13617 invoked from network); 8 Nov 2003 03:06:35 -0000 Received: from 66-52-242-53.sttl.dial.netzero.com (HELO vangogh) (66.52.242.53) by smtp01.lax.untd.com with SMTP; 8 Nov 2003 03:06:35 -0000 From: "Brandon J. Van Every" To: "xconq" Subject: The gory Xconq kernel Date: Sat, 08 Nov 2003 03:10:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-SW-Source: 2003/txt/msg00606.txt.bz2 From: Hans Ronne [mailto:hronne@comhem.se] > > And the kernel is of course written in C. If you want to > write entirely new > games you would therefore in the end have to get your hands > dirty with C. > Either that or rewrite the kernel in your favourite language > (Python?). If > you want to give it a try, you are welcome to do so, 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! > but be warned: others > have tried before. The most serious attempt so far was made by Ed > Oskiewicz. He made sure Xconq would build under C++ (and > still maintain > compatibility with plain C). However, it is a big leap from there to > actually transform the kernel into object oriented code. And > it is a leap that cannot be taken in small steps. 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? 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. Cheers, www.indiegamedesign.com Brandon Van Every Seattle, WA Taking risk where others will not.