From mboxrd@z Thu Jan 1 00:00:00 1970 From: quanstro@labs.coraid.com (erik quanstrom) Date: Fri, 11 Nov 2011 11:09:47 -0500 Subject: [9fans] all you yacc experts In-Reply-To: References: Message-ID: Topicbox-Message-UUID: 3ec91d78-ead7-11e9-9d60-3106f5b1d025 On Fri Nov 11 11:08:13 EST 2011, rminnich at gmail.com wrote: > Go is pretty solid on 386 and I'm slowly puzzling my way through NIX support. > > One thing that stands in the way of full native build is the bison issue. > > If somebody wants to look at enhancing yacc so that the extra bison > bits can be supported, that would probably do the trick. I have no > idea of the level of effort, I have not looked. > > We could run bison under linuxemu; I don't think this approach is as > good because it still leaves us a bit dependent on some outside force > for bison binaries. But that might be a good stopgap. > > I'm looking forward to Go 1 because I'm pretty sure that most of what > we've had to do for this version of Go will go away :-) > > I'm still amused that the best way to write portable C is to just ship > a reasonable C compiler with Go and use gcc to build that C compiler, > and then compile your portable C with it :-) at one time the go .y wasn't bison dependent. is the new dependency a choice or requirement? - erik