unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Andrew Gwozdziewycz <apgwoz@gmail.com>
To: Keith Wright <kwright@keithdiane.us>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: C programs in Scheme syntax
Date: Fri, 29 May 2020 09:27:12 -0700	[thread overview]
Message-ID: <456E2DFA-825A-4C43-9686-0EE0C9AF4CE6@gmail.com> (raw)
In-Reply-To: <87pnantoe5.fsf@fcs20.keithdiane.us>

One might also take a look at PreScheme: https://en.wikipedia.org/wiki/Scheme_48 which is a lowlevel Sexp based system that can generate C or Bytecode. 

There’s also BitC, which was/is a sexp based lowlevel language. I cannot recall if it compiled directly to C, or was itself a compiler to machine code. 

These, both, are not direct answers to your question (which I think has a fairly straightforward answer), but might give you some alternative ideas to consider.

> On May 28, 2020, at 20:38, Keith Wright <kwright@keithdiane.us> wrote:
> 
> I am thinkging about a project that uses Scheme macros
> to generate C code.  To this end I want to encode C 
> programs as S-expressions.  For example, the C program
> that is encoded in Ascii as
> 
> for (j=0;j<12;++j) a[j] = j*pi/6;
> 
> might be encoded as an S-expression as
> 
> (for ((= j 0)(< j 12) (++ j)) (= (sub a j)(/ (* j pi) 6)))
> 
> Note that this is not a valid Scheme program, even with
> non-standard functions defined.  It is a re-encoding
> of the Ascii C syntax as an S-expression.
> 
> I think I have read about something like this, perhaps
> on this list, I am not sure.  (Note to future language
> inventors: a single letter name makes a horrible Google
> search query.  Name things with made up but pronouncable
> words---perl, fortran...)
> 
> I most need to convert S-expr encoded C, to Ascii encoded C,
> but I am interested in
> (a) programs to convert S-expresions to C
> (b) specifications for the form of the S-expr encoding
> (c) better plans; advice from those who have tried and failed.
> 
> Any pointers?
> 
>   -- Keith
> 
> 


  parent reply	other threads:[~2020-05-29 16:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-29  3:23 C programs in Scheme syntax Keith Wright
2020-05-29  3:57 ` John Cowan
2020-05-29  7:29   ` Arne Babenhauserheide
2020-05-29 12:34 ` Matt Wette
2020-05-29 15:30 ` Zelphir Kaltstahl
2020-05-29 16:27 ` Andrew Gwozdziewycz [this message]
2020-05-29 20:01 ` Jan Wedekind
2020-05-30 10:13   ` Todor Kondić
  -- strict thread matches above, loose matches on Subject: below --
2020-05-31 15:40 tantalum

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=456E2DFA-825A-4C43-9686-0EE0C9AF4CE6@gmail.com \
    --to=apgwoz@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=kwright@keithdiane.us \
    /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).