Re: Pending issues wrt integrating objc-improvements-branch withmainline

[Stan Shebs <shebs at apple dot com>]

Ziemowit Laski wrote:

> On 2 Aug, 2004, at 22.17, Stan Shebs wrote:
>
> > Ziemowit Laski wrote:
> >
> > > (1) How should I discharge my obligation regarding ObjC++  
> > > documentation?  Given that there is next to no _ObjC_ documentation
> > >     in GCC at present :-), I am tempted to simply point GCC users at
> > >
> > >          
> > > http://developer.apple.com/documentation/Cocoa/Conceptual/ObjectiveC/ 
> > > index.html
> > >
> > >     which discusses both ObjC and ObjC++.  Would this be OK, and if 
> > > so,  where should I insert it?
> >
> >
> > If I weren't so far behind, I could help more here, but my general
> > suggestion for this is to point at the ObjC book for the description
> > of ObjC proper, then add a couple pages at the end of chapter 6,
> > "Extensions to the C++ Language" that basically say "mutually
> > oblivious" in different ways and with examples. A simple enumeration
> > of what works and what doesn't should be pretty quick to compose,
> > since you presumably had that in your head while hacking. :-)
>
>
> Hmmm...  Don't know what you mean by "the book", but chances are it is 
> probably outdated by now (does it cover EH, for example?). :-)

Oops, confusingly ambiguous. By "chapter 6" I meant the one in the
GCC manual. Alternatively, we could generalize the "Objective-C
runtime features" chapter to be an overall description of GCC's
ObjC implementation, including ObjC++, leaving the old Apple manual
as the formal description of language proper, semantic gaps and all.

Stan