• 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
New ObjC feature was (Re: Is ObjC++ a Bad Thing?) on pbuser list
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

New ObjC feature was (Re: Is ObjC++ a Bad Thing?) on pbuser list


  • Subject: New ObjC feature was (Re: Is ObjC++ a Bad Thing?) on pbuser list
  • From: Gerard Iglesias <email@hidden>
  • Date: Wed, 18 Jun 2003 10:19:19 +0200

Not a language war here, but ...

On Tuesday, June 17, 2003, at 06:13 PM,
email@hidden wrote:

> How is it "unelegant (not to say disgusting)" to use the full power of
> the language available? Objective-C *started out* unelegant: it's the
> result of grafting Smalltalk syntax onto C. It has its virtues, but
> C++ *also* has its virtues.

Download WebCore and see that the use of ObjC++ has its virtues, true :)

> There are times when C++'s function overloading is useful.

Even if, as a old Math student, I beleived at the beginning that
operator overloading a good thing, I discovered that it is not a good
practice, too much things hidden under that.

> A good craftsman uses the best tools for the job, whatever those tools
> are.

Yes, but this argument is too easy to use, I think that it hide the
laziness of people to learn the use of a specific tool enough to be
able to do a lot of with it.

> I have yet to understand the fear and loathing that Objective-C
> fanatics feel towards C++.

I don't like to use C++ even if I made very big project with it in the
past, the sole thing that I miss in ObjC is the capability to create
light weight object, in fact a struct, and use them with the same
syntax as true dynamic, late binbding object.

I would want to be able to do this :

NSPoint thePoint = {10, 20};
NSPoint anOtherPoint = {5, 5};

[thePoint addPoint:anOtherPoint];
[thePoint drawDescriptionAtPosition:NSMakePoint(100, 20)]

All this stuff with no messaging overhead, because the compiler would
change that with direct function call, it would be very very nice.

I hate to pollute my code with function call because of lightweight
structure used in the code for efficiency.

Best regards

Gerard
_______________________________________________
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: NSAppleScript error that is not an error
  • Next by Date: NSImage drawInRect:
  • Previous by thread: Re: libcrypto warning
  • Next by thread: NSImage drawInRect:
  • Index(es):
    • Date
    • Thread