From: Nick Owens <mischief@offblast.org>
To: 9front@9front.org
Subject: Re: [9front] bug: cpp(1) token pasting failure
Date: Mon, 17 Sep 2018 04:53:30 -0700 [thread overview]
Message-ID: <CAH_zEu6FF50JFF-1cF6BkxrZtHWick_o3Vsypfmsb16iGiap=w@mail.gmail.com> (raw)
In-Reply-To: <1537179430.3579192.1510568832.09757815@webmail.messagingengine.com>
i believe macros can appear anywhere, but that particular output is
the result of cpp(1)'s token pasting failure - it is not the correct
output.
On Mon, Sep 17, 2018 at 3:17 AM Ethan Gardener <eekee57@fastmail.fm> wrote:
>
> On Sun, Sep 16, 2018, at 9:54 PM, Nick Owens wrote:
> > DEF_ASM(jo #undef DEF};static const char keywords[] = #define DEF(id,
> > str) str "\0" DEF_ASMTEST(j,)#undef DEF;int main(int argc, char
> > *argv[]){ return -1;}#line 23
>
> i thought you could only use preprocessor directives at the start of a line. i'm pretty sure i learned that particular point, but it was probably in the 90s.
prev parent reply other threads:[~2018-09-17 11:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-16 20:54 Nick Owens
2018-09-17 10:17 ` [9front] " Ethan Gardener
2018-09-17 11:53 ` Nick Owens [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='CAH_zEu6FF50JFF-1cF6BkxrZtHWick_o3Vsypfmsb16iGiap=w@mail.gmail.com' \
--to=mischief@offblast.org \
--cc=9front@9front.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 NNTP newsgroup(s).