> > > At the last LinuxWorld, Jean-Baptist Kempf of the VLC project > > > visited > > > our booth, and mentioned that they are planning on dropping the > > > BeOS > > > platform because it does not have support for C99 which will be a > > > requirement for the next version of VLC (I hope I got that right, > > > but > > > Urias can correct me if I am wrong). > > > > > > I don't know the (technical) implications of this new requirement > > > or > > > whether it is worthwhile to keep the BeOS port alive or go for a > > > "clean" Haiku port (as was mentioned on the Ruby port thread > > > recently). > > > > The VLC port is most likely different from Ruby or APR, in that it > > is > > not just a question of BeOS POSIX workarounds but probably also has > > a > > GUI based on the Be API. I've heard there are changes concerning > > the > > layouting in Haiku, but having them drop pre-C99 support while > > keeping > > the BeOS specific code for a migration to Haiku would sound easier. > > At the last GSoC mentor summit, I talked to a few guys from the VLC > project. > It sounded like they want to get rid of some places in the common code > where it is messy with #ifdef __BEOS__ stuff. From my point of view, > they should go ahead and clean those up, since that will most likely > be Actually submitting them a patch that removes net_server hacks but keeps it buildable under BONE might be an option. Most people use BONE anyway, and it would remove the most horendous hacks without removing BeOS as a valid target, to assure a smooth transition to Haiku later on. > posix code that we want to provide compatibility to in Haiku anyways, > if not already done. But they should keep the BeOS interface code in > their repo if they don't mind. That code is not messy at all and > should > not harm any other platforms until someone can pick up work on VLC > again. Though it seems current versions are likely not to build anyway... François.