[haiku-development] Re: To __BEOS__ or not to __BEOS__?

> Howdy,
> 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 lot
> of cases one has to (respectively it makes sense to) disable BeOS
> work-arounds in software that had been ported to BeOS before. What do
> you
> think about dropping __BEOS__?

I thought we wanted to be source and binary compatible with BeOS for
doing so before R1 would break source level compatibility, so I would
avoid doing that.


Other related posts: