Re: ObjC/ObjC++: updated documentation on supported standards, and added -fobjc-std=objc1

["Nicola Pero" <nicola dot pero at meta-innovation dot com>]

> .. the only issue with using 'std' is that there are no 'standards' as  
> such

Yes. :-)

But I'd like to use "std" in the name because it does the same things that 
-std=... does for C/C++: it makes the compiler conform to a certain dialect
of the language.  In this case, the dialect ("Objective-C 1.0") is specified 
by referring to a reference implementation (GCC 4.0).  I'd say that is the
same as what an option like -std=gnu89 does.  Most GCC users are aware of 
-std=c90 and similar and it makes sense for them to have an option with
a similar name (-fobjc-std=...) for the Objective-C dialect.  (it could be
argued that it should be -objc-std=... to be more similar to -std=...)

If we don't want to use "std", maybe I'd be happy with -fobjc-dialect=xxx.

Else, we can always stick with -fobjc-std=objc1.

Thanks