[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: import vs include Re: Porting autogsdoc to OSX
From: |
Pascal Bourguignon |
Subject: |
Re: import vs include Re: Porting autogsdoc to OSX |
Date: |
Wed, 27 Feb 2002 12:17:45 +0100 (CET) |
> From: Peter Cooper <comrade@obverse.com.au>
> Date: Wed, 27 Feb 2002 12:11:09 +0100
>
> > 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.
What about just compiling with -DSTRICT_OPENSTEP?
Well, last time I checked, it had problems... This should be
addressed; I'll test again with a fresh cvs update.
--
__Pascal_Bourguignon__ (o_ Software patents are endangering
() ASCII ribbon against html email //\ the computer industry all around
/\ and Microsoft attachments. V_/ the world http://lpf.ai.mit.edu/
1962:DO20I=1.100 2001:my($f)=`fortune`; http://petition.eurolinux.org/
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS/IT d? s++:++(+++)>++ a C+++ UB+++L++++$S+X++++>$ P- L+++ E++ W++
N++ o-- K- w------ O- M++$ V PS+E++ Y++ PGP++ t+ 5? X+ R !tv b++(+)
DI+++ D++ G++ e+++ h+(++) r? y---? UF++++
------END GEEK CODE BLOCK------
- Re: import vs include Re: Porting autogsdoc to OSX, (continued)
- Re: import vs include Re: Porting autogsdoc to OSX, Nicola Pero, 2002/02/27
- Re: import vs include Re: Porting autogsdoc to OSX, Marcus Müller, 2002/02/27
- Re: import vs include Re: Porting autogsdoc to OSX, Richard Frith-Macdonald, 2002/02/27
- Re: import vs include Re: Porting autogsdoc to OSX, Helge Hess, 2002/02/27
- Re: import vs include Re: Porting autogsdoc to OSX, Richard Frith-Macdonald, 2002/02/27
- Re: import vs include Re: Porting autogsdoc to OSX, Peter Cooper, 2002/02/27
- Re: import vs include Re: Porting autogsdoc to OSX,
Pascal Bourguignon <=
- Re: import vs include Re: Porting autogsdoc to OSX, Dirk Theisen, 2002/02/27
- Re: import vs include Re: Porting autogsdoc to OSX, Richard Frith-Macdonald, 2002/02/27
- Re: import vs include Re: Porting autogsdoc to OSX, Richard Frith-Macdonald, 2002/02/27
- Re: import vs include Re: Porting autogsdoc to OSX, Helge Hess, 2002/02/27
- Re: import vs include Re: Porting autogsdoc to OSX, Richard Frith-Macdonald, 2002/02/27
- Re: import vs include Re: Porting autogsdoc to OSX, Pascal Bourguignon, 2002/02/27
- Re: import vs include Re: Porting autogsdoc to OSX, Richard Frith-Macdonald, 2002/02/27
- Re: import vs include Re: Porting autogsdoc to OSX, Dirk Theisen, 2002/02/27
- Re: import vs include Re: Porting autogsdoc to OSX, Nicola Pero, 2002/02/27
- Re: import vs include Re: Porting autogsdoc to OSX, Dirk Theisen, 2002/02/27