• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Georg looks at that Georg! ;-)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Georg looks at that Georg! ;-)


  • Subject: Re: Georg looks at that Georg! ;-)
  • From: John Hörnkvist <email@hidden>
  • Date: Sun, 9 Mar 2003 12:53:19 +0100

On Tuesday, March 4, 2003, at 09:39 AM, email@hidden wrote:
No, seriously, don't start a religious C/C++/Obj-C war,
at least not for me because anyway, I use Obj-C and I
enjoy it.
So C++ is not an object oriented language? So be it! It
is
just a matter of label if not a matter of taste.

Well, C++'s model is probably better described as "class based" than "object oriented".

I've given in and usually call C++ a static object oriented language, as opposed to Objective-C which is a dynamic object oriented language.

The ability to use objects really helps during the design phase. I think dynamism mostly helps maintenance --- and in any non-trivial project you spend most of your time rewriting rather than writing.

Well, let's stop this thread, and again many thanks to
the people go gave me very informative hints about
Obj-C.

There's a paper called "The cost of being object-oriented: A preliminary study" (See http://citeseer.nj.nec.com/budimlic98cost.html). There they compare LINPACK style programs machine translated from Fortran to Java with programs written in "good" OO-style and an intermediate (Light OO) way. I think it's fairly educational since it looks at the same algorithms implemented in the same language but in different ways.

It's worth considering that while the object oriented style often gives clean programs that are easy to develop and maintain, there are costs associated not only with message passing, but also with the data organization it brings. The way data is modeled may not be optimal from a performance viewpoint. This probably matters in less than a percent of the code we write, but now and then rewriting an OO-model in a "flat" or disassociated way makes a huge difference. However, the strength of a clean object oriented design is that you can usually flatten the model underneath, and the rest of the application can be unchanged...

Regards,
John Hornkvist
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Prev by Date: Re: Never ending lack of memory
  • Next by Date: Re: Never ending lack of memory
  • Previous by thread: Re: Georg looks at that Georg! ;-)
  • Next by thread: Image Filtering Services
  • Index(es):
    • Date
    • Thread