From: C H Forsyth <forsyth@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] C compiler bug?
Date: Tue, 8 Feb 2005 15:08:28 +0000 [thread overview]
Message-ID: <46fe329ee96d5070f6604bbe5da5da45@vitanuova.com> (raw)
In-Reply-To: <4d95201587124bf36889be11b7effcce@hamnavoe.com>
[-- Attachment #1: Type: text/plain, Size: 34 bytes --]
i think i've got a fix for that.
[-- Attachment #2: Type: message/rfc822, Size: 2213 bytes --]
From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@cse.psu.edu
Subject: [9fans] C compiler bug?
Date: Tue, 8 Feb 2005 09:37:23 0000
Message-ID: <4d95201587124bf36889be11b7effcce@hamnavoe.com>
Or misunderstanding?
term% cat t.c
#define STRING "//foo"
main()
{
print(STRING);
}
term% 8c t.c
t.c:6 newline in string
t.c:6 syntax error, last name: "<string>"
term%
next prev parent reply other threads:[~2005-02-08 15:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 9:37 Richard Miller
2005-02-08 9:44 ` geoff
2005-02-08 15:08 ` C H Forsyth [this message]
2005-02-08 15:43 ` Lucio De Re
2005-02-08 19:55 ` Bruce Ellis
2005-02-08 22:50 ` Charles Forsyth
2005-02-09 5:28 ` Lucio De Re
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=46fe329ee96d5070f6604bbe5da5da45@vitanuova.com \
--to=forsyth@vitanuova.com \
--cc=9fans@cse.psu.edu \
/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).