gnustep/tools-make
0
0
Fork 0
mirror of https://github.com/gnustep/tools-make.git synced 2025-04-22 22:00:49 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Updated doc to say that MacOS X uses #import as well

Browse source 
git-svn-id: svn+ssh://svn.gna.org/svn/gnustep/tools/make/trunk@12873 72102866-910b-0410-8b05-ffd578937521
This commit is contained in:
Nicola Pero 2002-02-28 10:58:54 +00:00
parent 574caa3a29
commit 8442d1cbce
3 changed files with 26 additions and 18 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
ChangeLog
View file

@ -1,3 +1,9 @@
Thu Feb 28 10:57:14 2002 Nicola Pero <nicola@brainstorm.co.uk>
* Documentation/install.texi (Warnings for deprecated #import):
Say that MacOS X uses #import.
* INSTALL: Regenerated.
2002-02-28 Richard Frith-Macdonald <rfm@gnu.org>
* configure.in: Set default user root to $HOME/GNUstep as a

19
Documentation/install.texi
View file

@ -128,21 +128,22 @@ CFLAGS="-I/usr/local/include" ./configure --with-thread-lib="-L/usr/local/lib -l
@subsection Warnings for deprecated #import
The #import directive, often found in legacy Objective-C code from the
NeXTstep and OpenStep era, is deprecated. You should use #include
NeXTstep and OpenStep era (and more recently on code from the Apple
MacOS X Cocoa environment), is deprecated. You should use #include
instead whenever possible, and even if you use #import, you should
protect all your headers against multiple inclusions. The GCC compiler
automatically emits a warning whenever you use #import. For political
and historical reasons (basically for fear of annoying legacy users),
these warnings are disabled by gnustep-make. But if you are not a
legacy user and/or you want to make sure your Objective-C code is not
using any deprecated feature, you should configure gnustep-make with
--disable-import:
and historical reasons (basically for fear of annoying legacy and MacOS
X users), these warnings are disabled by gnustep-make. But if you are
not a legacy (/MacOS X) user and/or you want to make sure your
Objective-C code is not using any deprecated feature, you should
configure gnustep-make with --disable-import:
@example
./configure --disable-import
@end example
If you are a legacy user, and wonder why #import is deprecated, please
search the web and the GCC and GNUstep mailing list archives - there are
very precise and sound technical reasons.
If you are a legacy or MacOS X user, and wonder why #import is
deprecated, please search the web and the GCC and GNUstep mailing list
archives - there are very precise and sound technical reasons.
@node Cross-Compiling, Flat Structure, Warnings for deprecated #import, Configuration
@subsection Configuring the GNUstep makefile package for a cross-compile target

19
INSTALL
View file

@ -100,19 +100,20 @@ Warnings for deprecated #import
-------------------------------
The #import directive, often found in legacy Objective-C code from
the NeXTstep and OpenStep era, is deprecated. You should use #include
the NeXTstep and OpenStep era (and more recently on code from the Apple
MacOS X Cocoa environment), is deprecated. You should use #include
instead whenever possible, and even if you use #import, you should
protect all your headers against multiple inclusions. The GCC compiler
automatically emits a warning whenever you use #import. For political
and historical reasons (basically for fear of annoying legacy users),
these warnings are disabled by gnustep-make. But if you are not a
legacy user and/or you want to make sure your Objective-C code is not
using any deprecated feature, you should configure gnustep-make with
-disable-import:
and historical reasons (basically for fear of annoying legacy and MacOS
X users), these warnings are disabled by gnustep-make. But if you are
not a legacy (/MacOS X) user and/or you want to make sure your
Objective-C code is not using any deprecated feature, you should
configure gnustep-make with -disable-import:
./configure --disable-import
If you are a legacy user, and wonder why #import is deprecated,
please search the web and the GCC and GNUstep mailing list archives -
there are very precise and sound technical reasons.
If you are a legacy or MacOS X user, and wonder why #import is
deprecated, please search the web and the GCC and GNUstep mailing list
archives - there are very precise and sound technical reasons.
Configuring the GNUstep makefile package for a cross-compile target
-------------------------------------------------------------------