Linked by Thom Holwerda on Sun 10th Sep 2006 20:38 UTC, submitted by fudel
Permalink for comment 161311
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
More News »
Sponsored Links



Member since:
2006-01-01
Vanders, BeOS doesn't use versioned Shared Objects for System libs. This then kills your entire point. BeOS != LINUX.
JT is right on this one. Listen to him.
To include the entire API again would needlessly expand the entire install base. If you are breaking binary compatibility, it should be all or nothing IMO. (Isn't that what Syllable dod to the original libAtheos.so?) You then have issues like linking drivers to the Kernel, input filters to the input server, various bits and pieces to the App server. That's just the tip of the iceberg.
I've looked at writing a thunking layer for BeOS to allow GCC 3.x to be used in plain R5.03. Way, way too much work.