From: Lucio De Re <lucio@proxima.alt.za>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan 9 Go (Was: GNU/Linux/Plan 9 disto)
Date: Fri, 22 Jul 2011 20:08:33 +0200 [thread overview]
Message-ID: <20110722180833.GE2065@fangle.proxima.alt.za> (raw)
In-Reply-To: <a5afad0cd57a5319112ccfe4fd6fe78b@coraid.com>
On Fri, Jul 22, 2011 at 01:53:41PM -0400, erik quanstrom wrote:
> can you give am example where // comments with ' cause
> trouble. i can't replicate.
>
I don't have an example ready at hand.
Russ correctly points out that the problem lies with cpp and not with 8c,
while careful inspection of the yacc sources including your correction to
accept // does not reveal any way in which yacc can be held responsible.
But I do not use cpp in the Go port so I have no idea why I encounter
the same problem as Bakul. Just to be even more explicit, I used pcc to
compile cmd/gc/mkbuiltin1.c and it failed, as expected. I have modified
mkbuiltin1.c to compile under 8c now, the problem has been resolved.
Weird, but I haven't yet reached a point where I can investigate this
to greater depth.
++L
next prev parent reply other threads:[~2011-07-22 18:08 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 5:36 arnold
2011-07-22 6:33 ` Lucio De Re
2011-07-22 7:42 ` Bakul Shah
2011-07-22 9:49 ` Lucio De Re
2011-07-22 12:41 ` erik quanstrom
2011-07-22 13:03 ` Lucio De Re
2011-07-22 15:13 ` erik quanstrom
2011-07-22 15:37 ` Lucio De Re
2011-07-22 17:13 ` Bakul Shah
2011-07-22 17:53 ` erik quanstrom
2011-07-22 18:08 ` Lucio De Re [this message]
2011-07-22 18:20 ` erik quanstrom
2011-07-22 18:32 ` Skip Tavakkolian
2011-07-22 19:04 ` Lucio De Re
2011-07-22 18:54 ` Lucio De Re
2011-07-22 18:22 ` ComeauAt9Fans@gmail.com
2011-07-22 18:32 ` erik quanstrom
2011-07-22 18:57 ` Lucio De Re
2011-07-22 18:38 ` Bakul Shah
2011-07-22 18:45 ` erik quanstrom
2011-07-22 18:48 ` ComeauAt9Fans@gmail.com
2011-07-22 18:53 ` erik quanstrom
2011-07-22 19:08 ` tlaronde
2011-07-22 18:55 ` Bakul Shah
2011-07-22 19:09 ` erik quanstrom
2011-07-22 19:42 ` Bakul Shah
2011-07-23 9:14 ` erik quanstrom
2011-07-23 13:24 ` Lucio De Re
2011-07-22 19:13 ` Lucio De Re
2011-07-22 15:39 ` Bakul Shah
2011-07-22 15:43 ` erik quanstrom
2011-07-22 16:35 ` Steve Simon
2011-07-22 17:53 ` Lucio De Re
2011-07-22 18:03 ` Lucio De Re
2011-07-22 18:30 ` Ethan Grammatikidis
2011-07-22 18:33 ` erik quanstrom
2011-07-22 18:53 ` ComeauAt9Fans@gmail.com
2011-07-22 19:00 ` Lucio De Re
2011-07-22 20:10 ` Ethan Grammatikidis
2011-07-22 22:59 ` Russ Cox
2011-07-23 11:16 ` Ethan Grammatikidis
2011-07-22 17:48 ` Lucio De Re
2011-07-22 18:17 ` Ethan Grammatikidis
2011-07-22 19:40 ` Bakul Shah
-- strict thread matches above, loose matches on Subject: below --
2011-07-22 8:18 arnold
2011-07-15 8:51 Alex Brainman
2011-07-11 16:59 [9fans] GNU/Linux/Plan 9 disto Gorka Guardiola
2011-07-11 19:31 ` Charles Forsyth
2011-07-12 5:59 ` Pavel Zholkover
2011-07-12 15:13 ` [9fans] Plan 9 Go (Was: GNU/Linux/Plan 9 disto) Lucio De Re
2011-07-12 18:35 ` Francisco J Ballesteros
2011-07-13 18:31 ` Lucio De Re
2011-07-13 18:45 ` Lucio De Re
2011-07-14 18:59 ` stephano zanzin
2011-07-14 20:21 ` Lucio De Re
2011-07-14 20:35 ` Iruatã Souza
2011-07-15 2:37 ` Fazlul Shahriar
2011-07-22 4:40 ` Lucio De Re
2011-07-22 14:37 ` Ethan Grammatikidis
2011-07-27 2:55 ` kokamoto
2011-07-12 18:44 ` Skip Tavakkolian
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=20110722180833.GE2065@fangle.proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@9fans.net \
/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).