On Sun, Jan 6, 2019 at 2:27 PM Eric S. Raymond <e...@thyrsus.com> wrote:
> But for both of them our intended strategy is *not* to preprocess. > Instead, we're willing to accept that some abuses of the preprocessor > need to be punted to a human, but treat other uses as part of the > parse tree. I'm afraid that a lot, if not most of existing C code, even when simple, clean and preprocessor-abuse-free, cannot be parsed before preprocessing. -- -j -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
