[haiku-development] Re: Coding style conflicting with API
- From: François Revol <revol@xxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Mon, 19 Nov 2012 09:27:03 +0100
On 19/11/2012 00:52, Ingo Weinhold wrote:
>>> The same could be said about POSIX. They pollute the global
>>> namespace, and so do we. I think all we can do about this is
>>> exporting only weak symbols. Renaming would work, too, but I'm not
>>> sure this really is a necessity.
>
> Yeah, the POSIX API is somewhat similar with respect to this problem. A
> difference is that the BeOS/Haiku API is significantly less known.
> Ported software (i.e. the majority of software available for Haiku) is
> likely using or at least aware of the POSIX API.
>
> Linkage is only part of the problem, BTW. Ported software that needs to
> use Haiku specific API will likely include <OS.h> and thus pull in lots
> of API declarations that may clash with internal declarations of that port.
By experience this doesn't happen often but it does.
I recall having to #redefine focus_follows_mouse() in the XEmacs port.
François.
Other related posts:
