public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Eljay Love-Jensen <eljay@adobe.com>
To: gcc-help@gcc.gnu.org
Subject: new computer language with GCC
Date: Sat, 20 Mar 2004 17:54:00 -0000	[thread overview]
Message-ID: <6.0.3.0.2.20040319123333.01f7b2f8@iplan-mn.corp.adobe.com> (raw)
In-Reply-To: <s3roeqsbuwz.fsf@xmission.xmission.com>

Hello everyone,

I would like to try my hand at implementing a computer language in GCC.

The language is "lambda calculus brainf---".  Yes, "brainf---" is a dirty 
word.  And best of all, it's a VERY VERY SIMPLE language.  (Look it up in 
Google.  Amazingly terse.)

Does anyone know of a good "Idiot's Guide to Get Your Pet Programming 
Language Working With GCC As The Backend"?  An O'Reilly book or a HowTo URL?

I've been through the Compilers (Aho, Sethi, Ulman) "dragon" book.  I'd 
like to try my hand at the real thing.

I don't have any delusions that I'll be the next Niklaus Wirth.  I don't 
think anyone will be as prolific as he has been in formulating programming 
languages.

I could write a LCB --> C translator.  But that's a CFront kind of 
solution; I want to get some experience working with GCC.

Thanks,
--Eljay

  reply	other threads:[~2004-03-19 18:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-17 22:17 visibility attribute not supported?! Jeremy Kolb
2004-03-19 10:33 ` llewelly
2004-03-19 17:37   ` Jeremy Kolb
2004-03-19 20:24     ` llewelly
2004-03-20 17:54       ` Eljay Love-Jensen [this message]
2004-03-20 18:27         ` new computer language with GCC llewelly
2004-03-21 11:27           ` Eljay Love-Jensen
2004-03-21 19:50         ` Crafting Better Source Code in C++ Eljay Love-Jensen
2004-03-22  4:50           ` llewelly

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=6.0.3.0.2.20040319123333.01f7b2f8@iplan-mn.corp.adobe.com \
    --to=eljay@adobe.com \
    --cc=gcc-help@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).