From: <tomas@tuxteam.de>
To: Olivier Dion <olivier.dion@polymtl.ca>
Cc: guile-user@gnu.org
Subject: Re: good papers on graphics in scheme/lisp?
Date: Wed, 2 Mar 2022 18:42:16 +0100 [thread overview]
Message-ID: <Yh+seIljs2vHgBRc@tuxteam.de> (raw)
In-Reply-To: <875yow5kd3.fsf@laura>
[-- Attachment #1: Type: text/plain, Size: 947 bytes --]
On Wed, Mar 02, 2022 at 12:34:32PM -0500, Olivier Dion via General Guile related discussions wrote:
> On Wed, 02 Mar 2022, Blake Shaw <blake@nonconstructivism.com> wrote:
[...]
> > Also, one last thing, I'm considering attempting to create a DSL that
> > compiles to a subset of GLSL like Chicken's GLLS library[4], as I'm
> > becoming more and more interested in compilation. I remember reading
> > somewhere about a Guile library that allows you to write C in Guile,
>
> I think you are refering to
> <http://sph.mn/computer/guides/c/c-indent.html>.
>
> There's also <https://www.nongnu.org/nyacc/> that can be helpful if
> you're familiar with LALR(1) parsers.
Actually NYACC comes with a pretty complete C99 compiler [1], which is
used to generate FFI bindings. So perhaps using that as a stepping stone
towards GLSL doesn't sound that crazy...
Cheers
[1] https://www.nongnu.org/nyacc/nyacc-c99-ug.html
--
t
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2022-03-02 17:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 16:56 good papers on graphics in scheme/lisp? Blake Shaw
2022-03-02 17:34 ` Olivier Dion via General Guile related discussions
2022-03-02 17:42 ` tomas [this message]
2022-03-02 18:12 ` Aleix Conchillo Flaqué
-- strict thread matches above, loose matches on Subject: below --
2022-03-03 11:36 Blake Shaw
2022-03-03 19:10 Blake Shaw
2022-03-03 19:29 Blake Shaw
2022-03-03 22:35 ` Matt Wette
2022-03-04 5:42 ` tomas
2022-03-04 18:18 Blake Shaw
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=Yh+seIljs2vHgBRc@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=guile-user@gnu.org \
--cc=olivier.dion@polymtl.ca \
/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).