From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 22 Jul 2011 20:08:33 +0200 From: Lucio De Re To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-ID: <20110722180833.GE2065@fangle.proxima.alt.za> References: <201107220536.p6M5agtv019617@freefriends.org> <20110722130310.GO1803@fangle.proxima.alt.za> <2f6021d419a7327afa4134cda0e6c88f@ladd.quanstro.net> <20110722153731.GQ1803@fangle.proxima.alt.za> <20110722171320.50A9CB827@mail.bitblocks.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: [9fans] Plan 9 Go (Was: GNU/Linux/Plan 9 disto) Topicbox-Message-UUID: 04e9119e-ead7-11e9-9d60-3106f5b1d025 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