On Thu, May 20, 2010 at 10:20 PM, Steven Bosscher <stevenb.gcc@gmail.com
> wrote:
On Thu, May 20, 2010 at 9:54 PM, IainS <developer@sandoe-acoustics.co.uk
> wrote:
No Asbestos required - but .. I do have some observations..
I write pretty much all my serious (day-job) code in ObjC and..
... I have stated that it's an intention to make *that*, at least
work at
V2 on FSF.
Having said that:
a) I have not anything like as much attachment to ObjC++ ...
b) We are all limited in the amount of time we can allocate to
FSF ..
Right. I am not suggesting ObjC should go away at all. It clearly has
users and it's pretty much isolated. It mixes with the C front end,
of
course, but that is not a problem. With ObjC++, you have a front end
trying to unify the C, ObjC, and C++ front ends with itself. That's
not even comparable.
Besides, the ObjC language makes sense, whereas Obj-C++ combines the
worst of ObjC with the worst of C++ (or so I'm told by people who
should know what they're talking about ;-)
I thought Obj-C++ was most about ObjC - C++ interoperability
because all the OS-X UI runtime is written in ObjC which makes
it hard to write a pure C++ GUI application.