From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Matt Wette <matt.wette@gmail.com>
Cc: Guile User <guile-user@gnu.org>
Subject: libguile/eval.c: parse failed on input "x37" [WAS: [ANN] nyacc 0.80.3 released]
Date: Mon, 24 Jul 2017 14:59:09 +0200 [thread overview]
Message-ID: <877eyygfdu.fsf@gnu.org> (raw)
In-Reply-To: <2D72B3FB-6075-4F56-8698-6AC5BA96B2C0@gmail.com> (Matt Wette's message of "Sun, 18 Jun 2017 15:07:58 -0700")
Matt Wette writes:
The below condensed excerpt from Guile's eval.c gives
(unknown):1: parse failed at state 299, on input "x37"
scaffold/tests/t.c:55: C99 parse error
This looks pretty tricky and I'm not really working on this atm, just
thought to let you know.
Greetings,
janneke
typedef int scm_t_bits;
typedef int scm_t_cell;
typedef int *SCM;
#define SCM_UNPACK(x) ((scm_t_bits) (x))
#define SCM_UNPACK_POINTER(x) ((scm_t_bits *) (SCM_UNPACK (x)))
#define SCM_PACK_POINTER(x) (SCM_PACK ((scm_t_bits) (x)))
#define SCM2PTR(x) ((scm_t_cell *) (SCM_UNPACK_POINTER (x)))
#define SCM_GC_CELL_OBJECT(x, n) (((SCM *)SCM2PTR (x)) [n])
#define SCM_GC_CELL_WORD(x, n) (SCM_UNPACK (SCM_GC_CELL_OBJECT ((x), (n))))
#define SCM_CELL_WORD(x, n) SCM_GC_CELL_WORD ((x), (n))
#define SCM_CELL_WORD_0(x) SCM_CELL_WORD ((x), 0)
#define SCM_CELL_TYPE(x) SCM_CELL_WORD_0 (x)
#define SCM_IMP(x) (6 & SCM_UNPACK (x))
#define SCM_NIMP(x) (!SCM_IMP (x))
#define SCM_HEAP_OBJECT_P(x) (SCM_NIMP (x))
#define SCM_TYP7(x) (0x7f & SCM_CELL_TYPE (x))
#define SCM_HAS_HEAP_TYPE(x, type, tag) \
(SCM_NIMP (x) && type (x) == (tag))
#define SCM_HAS_TYP7(x, tag) (SCM_HAS_HEAP_TYPE (x, SCM_TYP7, tag))
#define scm_tc7_atomic_box 0x37
int
main ()
{
return SCM_HAS_TYP7 (0, scm_tc7_atomic_box);
}
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
prev parent reply other threads:[~2017-07-24 12:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-18 22:07 [ANN] nyacc 0.80.3 released Matt Wette
2017-07-24 12:35 ` 0ULL [WAS: [ANN] nyacc 0.80.3 released] Jan Nieuwenhuizen
2017-07-24 12:49 ` Unexpected extra parens on struct-ref " Jan Nieuwenhuizen
2017-07-24 12:52 ` Jan Nieuwenhuizen
2017-07-24 12:59 ` Jan Nieuwenhuizen [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=877eyygfdu.fsf@gnu.org \
--to=janneke@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).