At the risk of sound snippy, we've been over this several times and have elected, for pragmatic reasons, to do our best to maintain binary compatibility for the first release -- which rules out GCC3.x for the time being. This does *not*, however, rule out moving to it at a later date -- or even providing a parallel set of libraries which have been built with GCC3.x (just a "for instance"; no flames, please). Folks keep insisting on thinking we've maneuvered ourselves into a dead-end by striving for binary compatability at this time, and that just isn't the case! I respect Nathan's perspective (as well as his ability), but aside from whether or not we successfully achieve binary compatibility, this is a total non-issue. e Alex Jeppesen wrote: > > Read this article at http://www.beunited.org/index.php?beos_reform > its about re-creating beos. it made a good point about how binary > compatability will make it so you cannot use gcc 3.0 This is a big big > problem i belive. v3.0 produces better code on many levels and i think its > worth it to move on up. Anyone else? What do the OpenBeOS ppl think?