From: "Brandon J. Van Every" <vanevery@indiegamedesign.com>
To: "xconq" <xconq7@sources.redhat.com>
Subject: Python in Xconq
Date: Tue, 18 Nov 2003 05:17:00 -0000 [thread overview]
Message-ID: <OOEALCJCKEBJBIJHCNJDOEODGLAB.vanevery@indiegamedesign.com> (raw)
In-Reply-To: <001001c3ad82$e12fdd30$6401a8c0@Win2k>
From: Erik Jessen [mailto:ejessen@adelphia.net]
>
> I think having an interpreted language (v. the current Lisp-format
> datafile) would put Xconq way ahead of the competition (like ADC2 et
> al).
I agree. Adding Python support is my next agenda item after Windows UI.
I do not believe in Perl. It's ok for scripting, but it is a wholly
inappropriate language for building systems. Python can handle both
simple scripting and complex systems building. I'm not one to
eneumerate Python's many features, but for instance it has list
processing and hash tables / dictionaries built right into the language.
Cheers, www.indiegamedesign.com
Brandon Van Every Seattle, WA
Taking risk where others will not.
next prev parent reply other threads:[~2003-11-18 4:26 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 15:42 Marketing Xconq? Bill Macon
2003-11-17 18:55 ` Marketing Xconq? + battle isle suggestion Andreas Bringedal
2003-11-17 22:04 ` better Windows UI Brandon J. Van Every
2003-11-18 3:12 ` Erik Jessen
2003-11-17 21:56 ` Marketing Xconq? Eric McDonald
2003-11-17 22:38 ` Brandon J. Van Every
2003-11-18 3:15 ` Erik Jessen
2003-11-18 3:39 ` New Interpreter (was RE: Marketing Xconq?) Eric McDonald
2003-11-18 4:01 ` Erik Jessen
2003-11-18 4:05 ` Eric McDonald
2003-11-18 10:37 ` setgid (was: RE: New Interpreter (was RE: Marketing Xconq?)) Lincoln Peters
2003-11-18 15:52 ` Jim Kingdon
2003-11-18 5:17 ` Brandon J. Van Every [this message]
2003-11-18 11:33 ` Python in Xconq Erik Jessen
2003-11-18 13:37 ` OT Python stuff (was RE: Python in Xconq) Mark A. Flacy
2003-11-19 15:08 ` Erik Jessen
2003-11-19 16:44 ` Bruno Boettcher
2003-11-19 17:58 ` Eric McDonald
2003-11-19 21:18 ` GDL, XML and others...Re: " Jakob Ilves
2003-11-19 23:13 ` Brandon J. Van Every
2003-11-20 5:12 ` Eric McDonald
2003-11-20 8:54 ` Bruno Boettcher
2003-11-20 11:01 ` Jakob Ilves
2003-11-20 11:19 ` Brandon J. Van Every
2003-11-20 12:59 ` Jakob Ilves
2003-11-20 13:54 ` One Hex Combat Resolution, and jeweled teeth Brandon J. Van Every
2003-11-20 17:06 ` Eric E Moore
2003-11-20 17:37 ` Jakob Ilves
2003-11-20 17:47 ` Emmanuel Fritsch
2003-11-20 19:53 ` Eric E Moore
2003-11-21 2:16 ` Eric McDonald
2003-11-21 3:03 ` What is Python really good for? Brandon J. Van Every
2003-11-20 11:36 ` GDL, XML and others...Re: OT Python stuff (was RE: Python in Xconq) Bruno Boettcher
2003-11-20 4:38 ` Erik Jessen
2003-11-20 10:19 ` cheating Brandon J. Van Every
2003-11-21 1:46 ` cheating Eric McDonald
2003-11-21 2:32 ` cheating Brandon J. Van Every
2003-11-21 9:30 ` Managing "Designers disgust". cheating Jakob Ilves
2003-11-21 9:33 ` Brandon J. Van Every
2003-11-21 12:36 ` Jakob Ilves
2003-11-21 14:28 ` Brandon J. Van Every
2003-11-19 22:14 ` OT Python stuff (was RE: Python in Xconq) Brandon J. Van Every
2003-11-20 3:10 ` Erik Jessen
2003-11-18 1:13 ` Marketing Xconq? Dr Eric Edward Moore
2003-11-18 1:31 ` Eric McDonald
2003-11-18 2:34 ` Lincoln Peters
2003-11-18 3:11 ` Eric McDonald
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=OOEALCJCKEBJBIJHCNJDOEODGLAB.vanevery@indiegamedesign.com \
--to=vanevery@indiegamedesign.com \
--cc=xconq7@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).