From: Matt Wette <matt.wette@gmail.com>
To: Guile User <guile-user@gnu.org>
Subject: Re: [ANN] nyacc 0.80.4 released
Date: Fri, 4 Aug 2017 10:38:49 -0700 [thread overview]
Message-ID: <C5236290-2334-454E-A427-6D59BC26925D@gmail.com> (raw)
In-Reply-To: <878tj2zgo6.fsf@gnu.org>
> On Aug 1, 2017, at 10:23 PM, Jan Nieuwenhuizen <janneke@gnu.org> wrote:
>
> Matt Wette writes:
>> For the FFI-helper I need to parse the rat’s nest under /usr/include
>> so I am catching more.
>
> Hah :-)
So I decided I should probably implement `__has_include' and `__has_include_next' (as well as `include_next').
So one more dive into the C preprocessor. I have it working for <stdio.h> but “foo.h” is giving me a
little trouble for some unknown reason.
I have also added `asm' syntax in expression context but not in declaration context (as used in macOS).
Matt
prev parent reply other threads:[~2017-08-04 17:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 23:47 [ANN] nyacc 0.80.4 released Matt Wette
2017-08-01 20:53 ` Jan Nieuwenhuizen
2017-08-01 23:10 ` Matt Wette
2017-08-02 5:23 ` Jan Nieuwenhuizen
2017-08-02 12:13 ` Matt Wette
2017-08-02 12:22 ` Matt Wette
2017-08-04 10:31 ` Jan Nieuwenhuizen
2017-08-04 17:38 ` Matt Wette [this message]
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=C5236290-2334-454E-A427-6D59BC26925D@gmail.com \
--to=matt.wette@gmail.com \
--cc=guile-user@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).