Re: import vs include Re: Porting autogsdoc to OSX

[Peter Cooper]

> Ah ... but we are trying to be compatible, not just use the same API.  
> As much as possible we want
> to avoid having to locate and link additional frameworks to do what on 
> MacOS is all in one.
> Not that there is anything particularly hard about linking in extra 
> libraries, but why confuse
> developers by providing frameworks which have the same API but different 
> functionality?

It certainly makes development using, say, Cocoa development docs or mass-
market books easier if APIs live in similar places ;)

On encouraging portable software, to assist people building cross-platform
apps, eg GNUstep -> OpenStep or GNUstep -> Cocoa it might be useful to have
some sort of source audit tool for portability. 

I suspect that a 100%-correct tool will be impossible to build, but
something that can flag most compatibility issues during development might
lead to more portable code being written. After all, not all developers
have access to the different platforms during the critical early
implementation phases.

Regards

Peter