public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Eric McDonald <mcdonald@phy.cmich.edu>
To: pessolo@freemail.it
Cc: Lee Wenzbauer <lwenzbauer1@yahoo.com>, <xconq7@sources.redhat.com>
Subject: Re: development languages
Date: Tue, 16 Dec 2003 01:48:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0312151456320.29785-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <16347.21647.101051.180247@gargle.gargle.HOWL>

Hi Klaus, others,

On Sat, 13 Dec 2003, klaus schilling wrote:

> Perl may still be useful for riting *.g files,
> like forging gdl tables from SQL databases via DBI/DBD

Good idea.
Actually, the idea of creating and maintaining these tables in a 
database is rather appealing. If you create the necessary tools 
(in Perl or whatever) to perform SQL queries and tabulate the 
results in GDL, I think I would be one of the users of those 
tools.

  Thanks,
   Eric

      reply	other threads:[~2003-12-15 20:00 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
2003-12-16  1:48     ` Eric McDonald [this message]

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=Pine.LNX.4.44.0312151456320.29785-100000@leon.phy.cmich.edu \
    --to=mcdonald@phy.cmich.edu \
    --cc=lwenzbauer1@yahoo.com \
    --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).