Go to the FreeLists Home Page Home Signup Help Login
 



[haiku-development] || [Date Prev] [05-2008 Date Index] [Date Next] || [Thread Prev] [05-2008 Thread Index] [Thread Next]

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

  • From: "Stefano Ceccherini" <stefano.ceccherini@xxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Tue, 6 May 2008 23:03:38 +0200
2008/5/6 Ingo Weinhold <ingo_weinhold@xxxxxx>:
> 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__?
>

Many things would have to be reported, in that case (also things that
now works correctly, like SDL, for example). But in the long run, I'd
like to drop it.





[ Home | Signup | Help | Login | Archives | Lists ]

All trademarks and copyrights within the FreeLists archives are owned by their respective owners.
Everything else ©2007 Avenir Technologies, LLC.