From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: a little question ...
Date: 28 Oct 1998 10:14:55 +0100 [thread overview]
Message-ID: <m3yaq1m4j4.fsf@sparky.gnus.org> (raw)
In-Reply-To: Dave Love's message of "27 Oct 1998 18:46:46 +0000"
Dave Love <d.love@dl.ac.uk> writes:
> I don't think g77 is really up to the job currently (though it was
> once traditional to write Lisp and similar systems in FORTRAN, not to
> mention the occasional OS); you probably want to get going on g95
> development initially.
Yeah; you're right. But I've been thinking about rewriting gcc itself
in Scheme, but I first have to write a Scheme compiler in Perl.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1998-10-28 9:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-22 18:30 PISTORI David
1998-10-22 20:18 ` Wes Hardaker
1998-10-24 4:59 ` Lars Magne Ingebrigtsen
1998-10-27 18:46 ` Dave Love
1998-10-28 9:14 ` Lars Magne Ingebrigtsen [this message]
1998-10-28 19:46 ` Dave Love
1998-11-04 3:15 ` Carl R. Witty
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=m3yaq1m4j4.fsf@sparky.gnus.org \
--to=larsi@gnus.org \
/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 NNTP newsgroup(s).