CbC/CbC_gcc: gcc/doc/objc.texi comparison

comparison gcc/doc/objc.texi @ 111:04ced10e8804

gcc 7

author	kono
date	Fri, 27 Oct 2017 22:46:09 +0900
parents	f6334be47118
children	84e7813d76e9

comparison

equal deleted inserted replaced

-:561a7518be6b
+:04ced10e8804
-@c Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
+@c Copyright (C) 1988-2017 Free Software Foundation, Inc.
-@c 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2010
-@c Free Software Foundation, Inc.
 @c This is part of the GCC manual.
 @c For copying conditions, see the file gcc.texi.
 @node Objective-C
 @comment  node-name,  next,  previous,  up
-@chapter GNU Objective-C features
+@chapter GNU Objective-C Features
 This document is meant to describe some of the GNU Objective-C
 features.  It is not intended to teach you Objective-C.  There are
 several resources on the Internet that present the language.
 * Messaging with the GNU Objective-C runtime::
 @end menu
 @c =========================================================================
 @node GNU Objective-C runtime API
-@section GNU Objective-C runtime API
+@section GNU Objective-C Runtime API
 This section is specific for the GNU Objective-C runtime.  If you are
 using a different runtime, you can skip it.
 The GNU Objective-C runtime provides an API that allows you to
 * Traditional GNU Objective-C runtime API::
 @end menu
 @c =========================================================================
 @node Modern GNU Objective-C runtime API
-@subsection Modern GNU Objective-C runtime API
+@subsection Modern GNU Objective-C Runtime API
 The GNU Objective-C runtime provides an API which is similar to the
 one provided by the ``Objective-C 2.0'' Apple/NeXT Objective-C
 runtime.  The API is documented in the public header files of the GNU
 Objective-C runtime:
 The header files contain detailed documentation for each function in
 the GNU Objective-C runtime API.
 @c =========================================================================
 @node Traditional GNU Objective-C runtime API
-@subsection Traditional GNU Objective-C runtime API
+@subsection Traditional GNU Objective-C Runtime API
 The GNU Objective-C runtime used to provide a different API, which we
 call the ``traditional'' GNU Objective-C runtime API.  Functions
 belonging to this API are easy to recognize because they use a
 different naming convention, such as @code{class_get_super_class()}
 (traditional API) instead of @code{class_getSuperclass()} (modern
 API).  Software using this API includes the file
 @file{objc/objc-api.h} where it is declared.
-The traditional API is deprecated but it is still supported in this
+Starting with GCC 4.7.0, the traditional GNU runtime API is no longer
-release of the runtime; you can access it as usual by including
+available.
-@file{objc/objc-api.h}.
-If you are using the traditional API you are urged to upgrade your
-software to use the modern API because the traditional API requires
-access to private runtime internals to do anything serious with it;
-for this reason, there is no guarantee that future releases of the GNU
-Objective-C runtime library will be able to provide a fully compatible
-@file{objc/objc-api.h} as the private runtime internals change.  It is
-expected that the next release will hide a number of runtime internals
-making the traditional API nominally supported but fairly useless
-beyond very simple use cases.
-Finally, you can not include both @file{objc/objc-api.h} and
-@file{objc/runtime.h} at the same time.  The traditional and modern
-APIs unfortunately have some conflicting declarations (such as the one
-for @code{Method}) and can not be used at the same time.
 @c =========================================================================
 @node Executing code before main
-@section @code{+load}: Executing code before main
+@section @code{+load}: Executing Code before @code{main}
 This section is specific for the GNU Objective-C runtime.  If you are
 using a different runtime, you can skip it.
 The GNU Objective-C runtime provides a way that allows you to execute
 * What you can and what you cannot do in +load::
 @end menu
 @node What you can and what you cannot do in +load
-@subsection What you can and what you cannot do in @code{+load}
+@subsection What You Can and Cannot Do in @code{+load}
 @code{+load} is to be used only as a last resort.  Because it is
 executed very early, most of the Objective-C runtime machinery will
 not be ready when @code{+load} is executed; hence @code{+load} works
 best for executing C code that is independent on the Objective-C
 above apply to classes defined in bundle.
 @node Type encoding
-@section Type encoding
+@section Type Encoding
 This is an advanced section.  Type encodings are used extensively by
 the compiler and by the runtime, but you generally do not need to know
 about them to use Objective-C.
 Here are some types and their encodings, as they are generated by the
 compiler on an i386 machine:
 @sp 1
-@multitable @columnfractions .25 .75
+@multitable @columnfractions .60 .40
 @item Objective-C type
 @tab Compiler encoding
 @item
 @smallexample
 int a[10];
 @tab @code{@{?=i[3f]b128i3b131i2c@}}
 @item
 @smallexample
 int a __attribute__ ((vector_size (16)));
 @end smallexample
-@tab @code{![16,16i]} (alignment would depend on the machine)
+@tab @code{![16,16i]} (alignment depends on the machine)
 @end multitable
 @sp 1
 In addition to the types the compiler also encodes the type
 * @@encode::
 * Method signatures::
 @end menu
 @node Legacy type encoding
-@subsection Legacy type encoding
+@subsection Legacy Type Encoding
 Unfortunately, historically GCC used to have a number of bugs in its
 encoding code.  The NeXT runtime expects GCC to emit type encodings in
 this historical format (compatible with GCC-3.3), so when using the
 NeXT runtime, GCC will introduce on purpose a number of incorrect
 In addition to that, the NeXT runtime uses a different encoding for
 bitfields.  It encodes them as @code{b} followed by the size, without
 a bit offset or the underlying field type.
 @node @@encode
-@subsection @@encode
+@subsection @code{@@encode}
 GNU Objective-C supports the @code{@@encode} syntax that allows you to
 create a type encoding from a C/Objective-C type.  For example,
 @code{@@encode(int)} is compiled by the compiler into @code{"i"}.
 @code{const}.  For example, @code{@@encode(const char*)} is valid and
 is compiled into @code{"r*"}, while @code{@@encode(bycopy char *)} is
 invalid and will cause a compilation error.
 @node Method signatures
-@subsection Method signatures
+@subsection Method Signatures
 This section documents the encoding of method types, which is rarely
 needed to use Objective-C.  You should skip it at a first reading; the
 runtime provides functions that will work on methods and can walk
 through the list of parameters and interpret them for you.  These
 @@implementation WeakPointer
 + (void)initialize
 @{
-class_ivar_set_gcinvisible (self, "weakPointer", YES);
+if (self == objc_lookUpClass ("WeakPointer"))
+class_ivar_set_gcinvisible (self, "weakPointer", YES);
 @}
 - initWithPointer:(const void*)p
 @{
 weakPointer = p;
 specifier to the string type description of the instance variable named
 as argument.
 @c =========================================================================
 @node Constant string objects
-@section Constant string objects
+@section Constant String Objects
 GNU Objective-C provides constant string objects that are generated
 directly by the compiler.  You declare a constant string object by
 prefixing a C constant string with the character @samp{@@}:
 constant string classes, neither the compiler nor the linker impose any
 restrictions in doing this.
 @c =========================================================================
 @node compatibility_alias
-@section compatibility_alias
+@section @code{compatibility_alias}
 The keyword @code{@@compatibility_alias} allows you to define a class name
 as equivalent to another class name.  For example:
 @smallexample
 @option{-fobjc-exceptions}.
 @c =========================================================================
 @node Fast enumeration
-@section Fast enumeration
+@section Fast Enumeration
 @menu
 * Using fast enumeration::
 * c99-like fast enumeration syntax::
 * Fast enumeration details::
 * Fast enumeration protocol::
 @end menu
 @c ================================
 @node Using fast enumeration
-@subsection Using fast enumeration
+@subsection Using Fast Enumeration
 GNU Objective-C provides support for the fast enumeration syntax:
 @smallexample
 id array = @dots{};
 @end smallexample
 @c ================================
 @node c99-like fast enumeration syntax
-@subsection c99-like fast enumeration syntax
+@subsection C99-Like Fast Enumeration Syntax
 A c99-like declaration syntax is also allowed:
 @smallexample
 id array = @dots{};
 Note that the option @option{-std=c99} is not required to allow this
 syntax in Objective-C.
 @c ================================
 @node Fast enumeration details
-@subsection Fast enumeration details
+@subsection Fast Enumeration Details
 Here is a more technical description with the gory details.  Consider the code
 @smallexample
 for (@var{object expression} in @var{collection expression})
 @end itemize
 @c ================================
 @node Fast enumeration protocol
-@subsection Fast enumeration protocol
+@subsection Fast Enumeration Protocol
 If you want your own collection object to be usable with fast
 enumeration, you need to have it implement the method
 @smallexample
 - (unsigned long) countByEnumeratingWithState: (NSFastEnumerationState *)state
 objects: (id *)objects
 count: (unsigned long)len;
 @end smallexample
 where @code{NSFastEnumerationState} must be defined in your code as follows:
 value to be of type @code{unsigned long}.  They could also be declared
 to be of type @code{unsigned int} and everything would still work.
 @c =========================================================================
 @node Messaging with the GNU Objective-C runtime
-@section Messaging with the GNU Objective-C runtime
+@section Messaging with the GNU Objective-C Runtime
 This section is specific for the GNU Objective-C runtime.  If you are
 using a different runtime, you can skip it.
 The implementation of messaging in the GNU Objective-C runtime is
 * Forwarding hook::
 @end menu
 @c =========================================================================
 @node Dynamically registering methods
-@subsection Dynamically registering methods
+@subsection Dynamically Registering Methods
 If @code{objc_msg_lookup()} does not find a suitable method
 implementation, because the receiver does not implement the required
 method, it tries to see if the class can dynamically register the
 method.
 @smallexample
 + (BOOL) resolveInstanceMethod: (SEL)selector;
 @end smallexample
 in the case of an instance method, or
 @smallexample
 + (BOOL) resolveClassMethod: (SEL)selector;
 @end smallexample
 @code{resolveClassMethod:} was added to the GNU Objective-C runtime in
 GCC version 4.6.
 @c =========================================================================
 @node Forwarding hook
-@subsection Forwarding hook
+@subsection Forwarding Hook
 The GNU Objective-C runtime provides a hook, called
 @code{__objc_msg_forward2}, which is called by
-@code{objc_msg_lookup()} when it can't find a method implementation in
+@code{objc_msg_lookup()} when it cannot find a method implementation in
 the runtime tables and after calling @code{+resolveInstanceMethod:}
 and @code{+resolveClassMethod:} has been attempted and did not succeed
 in dynamically registering the method.
 To configure the hook, you set the global variable
-@code{__objc_msg_foward2} to a function with the same argument and
+@code{__objc_msg_forward2} to a function with the same argument and
 return types of @code{objc_msg_lookup()}.  When
 @code{objc_msg_lookup()} can not find a method implementation, it
 invokes the hook function you provided to get a method implementation
 to return.  So, in practice @code{__objc_msg_forward2} allows you to
 extend @code{objc_msg_lookup()} by adding some custom code that is

Mercurial > hg > CbC > CbC_gcc

comparison gcc/doc/objc.texi @ 111:04ced10e8804