Hi Ingo, Am 06.05.2008 um 22:19 schrieb Ingo Weinhold:
from my experience with porting stuff to Haiku so far, I've come to see the fact that our gcc also defines __BEOS__ as quite a mixed blessing. In a lotof cases one has to (respectively it makes sense to) disable BeOSwork-arounds in software that had been ported to BeOS before. What do youthink about dropping __BEOS__?
I probably favor this as well... Where is it being defined? Can we disable it ourselves under Haiku and run some tests first before you remove it in SVN?
Andreas