From: 510046470588-0001@t-online.de (klaus schilling)
To: Eric McDonald <mcdonald@phy.cmich.edu>
Cc: Lee Wenzbauer <lwenzbauer1@yahoo.com>, xconq7@sources.redhat.com
Subject: Re: development languages
Date: Sun, 14 Dec 2003 04:50:00 -0000 [thread overview]
Message-ID: <16347.21647.101051.180247@gargle.gargle.HOWL> (raw)
In-Reply-To: <Pine.LNX.4.44.0312122259390.6182-100000@leon.phy.cmich.edu>
Eric McDonald writes:
> On Sun, 7 Dec 2003, Lee Wenzbauer wrote:
>
> > tried
> > modifying/writing scenarios in GDL and when they
> > didn't perform as expected I went hacking through the
> > ai code. IMHO if you can clean up and fortify GDL
> > then it is easy to write a perl module that would let
> > developers write in perl after they installed the
> > module. That way you don't exclude anybody.
>
> Well, if you want to see all the reasons why Perl may not be a
> suitable replacement for GDL, please see consult the list
> archives. We had a rather toasty flamewar over this (and quite a
> few other things) around the middle of November.
>
> If you are thinking about writing a Perl API for Xconq, then go
> for it. I can think of several other people on this list who would
> probably appreciate it, even though Python seemed to be a more
> popular choice (though it was not always clear whether it was
> being considered as an API for the Xconq engine, AI's, or a GDL
> replacement).
>
Perl may still be useful for riting *.g files,
like forging gdl tables from SQL databases via DBI/DBD
Klaus Schilling
next prev parent reply other threads:[~2003-12-13 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-07 23:54 Lee Wenzbauer
2003-12-13 4:40 ` Eric McDonald
2003-12-14 4:50 ` klaus schilling [this message]
2003-12-16 1:48 ` 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=16347.21647.101051.180247@gargle.gargle.HOWL \
--to=510046470588-0001@t-online.de \
--cc=lwenzbauer1@yahoo.com \
--cc=mcdonald@phy.cmich.edu \
--cc=pessolo@freemail.it \
--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).