> Could you comment on your changes at http://code.google.com/p/go-plan9/ ? > Can they be pushed to mainline ?
i don't think they can in total. we should push the silly print format fixes and the added USED() that 8c caught and gcc didn't. but there definately are some difficult bits. this hacked inclusion of stdio.h is a problem on plan 9. http://code.google.com/p/go-plan9/source/diff?spec=svnd6ec95bd4f9b2e9af2d10f08d9869aa2ca49d851&r=d6ec95bd4f9b2e9af2d10f08d9869aa2ca49d851&format=side&path=/src/cmd/8a/a.y my "solution" clearly ignored the problems in pushing back to the main line. but at least we have the problem identified. /src/cmd/8l/l.h has another problem. we need to figure out how to get the definitions for uint8, etc from "#include <u.h>" the defines i put in are just wrong, but the alternative is passing in -Isomedir with a <u.h> that includes the real u.h and then tweaks other stuff. that's just wronger. :-) a real solution would be one of 0 copy u.h; hack to taste 1 add the hacks to the real u.h 2 come to a concensus with go about what the defined-bit-width types should be called. change both plan 9 and go to conform. i'd vote for 2. it's harder that way, but i'd hate for go to feel like it was pasted on. but i'd like to know what everyone else thinks. - erik
