From: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
To: Matt Wette <matt.wette@gmail.com>
Cc: Guile User <guile-user@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: ffi-help: status to 19 Aug 2017
Date: Sat, 11 Nov 2017 00:04:35 +0100 [thread overview]
Message-ID: <CAGua6m1mRDBZQ2L7Z7Z+MyepEBvWa5NDLVDxkWQoNQYyuHR6Hg@mail.gmail.com> (raw)
In-Reply-To: <48B67310-F3D5-45AB-9443-9F70EC1F9EB0@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 944 bytes --]
I'm trying out the ffi help stuff.
1. It looks like 1.234f numeric constants is not lexed
2. characters constants can be included in #if preprocessor steps it looks,
3. character constants seam to follow L?'(\\.|[^\\'])+'
Regards
Stefan
references:
https://www.lysator.liu.se/c/ANSI-C-grammar-l.html
https://gcc.gnu.org/onlinedocs/cpp/If.html#If
On Fri, Nov 10, 2017 at 3:39 AM, Matt Wette <matt.wette@gmail.com> wrote:
>
> > On Nov 9, 2017, at 11:10 AM, Roel Janssen <roel@gnu.org> wrote:
> > I wanted to try ffi-helper on htslib, but I am confused on how to get
> > started. Where does the "compile-ffi" subcommand for "guild" come from?
> >
>
> And not sure I answered this question as intended. The `guild' command
> looks for a scm file with
> basename of the first argument in a subdirectory scripts/ in LOAD_PATH.
> So `guild compile-ffi foo.ffi'
> will execute `scripts/compile-ffi.scm' with argument `foo.ffi'.
>
> Matt
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 1918 bytes --]
next prev parent reply other threads:[~2017-11-10 23:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D30BE676-0171-4E8F-8CD0-B40A74B08850@gmail.com>
2017-08-19 15:30 ` ffi-help: status to 19 Aug 2017 Matt Wette
2017-09-08 3:32 ` ffi-help: #:use-ffi-module Matt Wette
2017-09-08 3:40 ` Matt Wette
2017-11-09 19:10 ` ffi-help: status to 19 Aug 2017 Roel Janssen
2017-11-10 1:00 ` Matt Wette
2017-11-10 2:34 ` Matt Wette
2017-11-10 2:39 ` Matt Wette
2017-11-10 23:04 ` Stefan Israelsson Tampe [this message]
2017-11-11 4:38 ` Matt Wette
2017-11-14 18:06 ` Ricardo Wurmus
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=CAGua6m1mRDBZQ2L7Z7Z+MyepEBvWa5NDLVDxkWQoNQYyuHR6Hg@mail.gmail.com \
--to=stefan.itampe@gmail.com \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=matt.wette@gmail.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).