From: mrs@wrs.com (Mike Stump)
To: egcs@egcs.cygnus.com, pip@cpu.khimaira.com
Subject: Re: New Language
Date: Wed, 31 Mar 1999 23:46:00 -0000 [thread overview]
Message-ID: <199903160336.TAA12332@kankakee.wrs.com> (raw)
Message-ID: <19990331234600.SdHV1nYCFUOGt-uRuQN38vnnE6YTk7Cr7RVZFXA76io@z> (raw)
> Date: Mon, 15 Mar 1999 19:21:54 -0500 (EST)
> From: <pip@cpu.khimaira.com>
> To: egcs@egcs.cygnus.com
> I have started looking into adding support for a new language. Is
> there anything in terms of documentation/references in particular
> that I should look at ?
Not a whole lot has been written about this. Kenner is rumored to
have written a document describing it... If you find a pointer to it,
be sure to get us to put in a link to it.
Basically all you have to do, it do up your parse, build tree codes to
represent the semantics of it, call expand_expr on it, and your done.
:-) Right Per? There are just a few missing pieces that you'd need to
learn before that will just work. Watching how C or C++ works is one
way to get started.
next reply other threads:[~1999-03-31 23:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-15 19:36 Mike Stump [this message]
[not found] ` < 199903160336.TAA12332@kankakee.wrs.com >
1999-03-16 15:45 ` Martin v. Loewis
1999-03-31 23:46 ` Martin v. Loewis
1999-03-31 23:46 ` Mike Stump
-- strict thread matches above, loose matches on Subject: below --
1999-03-15 18:41 pip
1999-03-16 7:38 ` Dave Love
1999-03-31 23:46 ` Dave Love
1999-06-15 10:56 ` Gerald Pfeifer
1999-06-17 13:10 ` Dave Love
1999-06-17 14:08 ` Joe Buck
1999-06-30 15:43 ` Joe Buck
1999-06-30 15:43 ` Dave Love
1999-06-30 15:43 ` Gerald Pfeifer
1999-03-31 23:46 ` pip
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=199903160336.TAA12332@kankakee.wrs.com \
--to=mrs@wrs.com \
--cc=egcs@egcs.cygnus.com \
--cc=pip@cpu.khimaira.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).