From: erik quanstrom <quanstro@quanstro.net>
To: comeauat9fans@gmail.com, 9fans@9fans.net
Subject: Re: [9fans] cc nit?
Date: Sun, 1 Jul 2012 12:57:14 -0400 [thread overview]
Message-ID: <a1d8f6452487ec6d7a3a68fad5a54bcb@ladd.quanstro.net> (raw)
In-Reply-To: <CAE9W7-gZsWHuspmwBw0qU_djkiDhAF6hA2zLU3Ms=xiO1j5LXQ@mail.gmail.c>
> On Sat, Jun 30, 2012 at 5:25 PM, erik quanstrom <quanstro@quanstro.net>wrote:
>
> > i haven't tracked down thie issue yet, but it appears that ?c
> > generate unparsable acid output
> >
> > ; cat > void.c
> > typedef struct PNOTIFY PNOTIFY
> >
> > struct PNOTIFY {
> > void emptiness;
> > };
> > <eot>; 8c -a void.c
> > void.c:1 not a function
> > void.c:5 syntax error, last name: emptiness
> > ...
>
>
>
> I'm not sure where this is documented, but, isn't the problem (not just
> syntactically) with the above the missing semicolon on the typedef line and
> not the void'ness issue?
that's true, i did miss the semicolon. but that was a copypasta problem;
the issue still exists.
- erik
prev parent reply other threads:[~2012-07-01 16:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-30 21:25 erik quanstrom
2012-06-30 21:33 ` Bakul Shah
2012-06-30 21:37 ` erik quanstrom
2012-06-30 22:15 ` Bakul Shah
2012-07-01 13:47 ` erik quanstrom
2012-07-01 16:54 ` Comeau At9Fans
2012-07-01 20:39 ` Charles Forsyth
2012-07-01 22:22 ` Comeau At9Fans
2012-07-01 22:32 ` Charles Forsyth
2012-07-01 22:34 ` Charles Forsyth
2012-07-02 0:21 ` Comeau At9Fans
2012-07-02 0:18 ` Comeau At9Fans
2012-07-02 7:42 ` Charles Forsyth
2012-07-02 7:45 ` Charles Forsyth
[not found] ` <CAE9W7-iFxd6ysP4cxRcGVuLT0n+SY2r4XjOTVpjpXi292v4WWQ@mail.gmail.c>
2012-07-01 22:45 ` erik quanstrom
2012-07-02 0:24 ` Comeau At9Fans
[not found] ` <CAE9W7-gZsWHuspmwBw0qU_djkiDhAF6hA2zLU3Ms=xiO1j5LXQ@mail.gmail.c>
2012-07-01 16:57 ` erik quanstrom [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a1d8f6452487ec6d7a3a68fad5a54bcb@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=comeauat9fans@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 NNTP newsgroup(s).