On 19 Jan 2009, at 15:41, Sean McBride wrote:
On 1/17/09 9:51 PM, Erik Buck said:
As far as I know, there is still no compiler in
the world that completely implements the ANSI/ISO C++ standard which
was ratified in 1998. If the standard hasn't been implemented in a
decade, something is amiss
On 1/17/09 9:51 PM, Erik Buck said:
>As far as I know, there is still no compiler in
>the world that completely implements the ANSI/ISO C++ standard which
>was ratified in 1998. If the standard hasn't been implemented in a
>decade, something is amiss.
I agree C++ is an overly complex beast... bu
> Therefore, I take issue with Scott Ribe because I don't think Cocoa
> can be implemented as we know it in C++.
Eh? That was my point:
...just as you can't "rewrite Cocoa in C++"...
--
Scott Ribe
scott_r...@killerbytes.com
http://www.killerbytes.com/
(303) 722-0567 voice
___
On 18/01/2009, at 1:51 PM, Erik Buck wrote:
Both Objective-C message sending and C++ virtual function calls
commonly prevent in-lining because the _compiler_ can not determine
which code will actually be called. If you use Objective-C message
sending or C++ virtual member functions, you f
In this forum, Scott Ribe recently wrote "...but just as you can't
"rewrite Cocoa in C++" as we've seen demanded by people who don't
really understand Objective-C..."
I claim that a relatively dynamic language is necessary to effectively
use Cocoa. I also claim to have very deep and thorou
