However, if you should write opening bracket and closing bracket always. So, it makes you keep go back to the point where you passed, and place an open bracket. If the call is something like this, then it is worse.

MyClass *aclass = [[MyClass alloc] init];

You may just start to write after = like this : My Class alloc] (Ah! I forgot the opening bracket! Let's go back)

[MyClass alloc] init] ( Ah! I forgot another one!

It looks like stupid thing, but it happens!

So.. I think the code sense should be extended to the point that it can solve this problem. If not, I prefer the C++.

That's a poor example of C++ useage. Any good developer will run away screaming from "magic numbers". Good practice is to name *all* variables and constants, thus mitigating the problem as stated. Having said that, I can see some limited utility in typing parameter names.

Erik Barzeski recently wrote in his blog: "I really, really like Objective-C's [square brackets] method of markup (whatever you wanna call it)." Cocoa's syntax owns pretty much everything I've used. I have used VisualBASIC, realBASIC, C++, PHP, and Coc...

I get to prefere objective C instead of C++ notation.

If you have a nosey through some of the more hip-'n'-happenin' contemporary sociocultural journals, you'll see copious square brackets put in there to funkify the traditional parenthetical asides. It's a typographical aesthetics thing. Some hard masculine edges to put some brawny machismo into your soft, feminine serif body text. So get some balls into your code, and use square brackets.

Oh, and curly brackets are soooo last millennium.

Assuming the formatting comes out looking right, this is how I like to write methods. It takes up more space, and is more typing, but as an amatuer programmer, I love the fact that the method call lets me know exactly whats going on. No need to look up the docs unless I need more details.

[someObject createConnectionToSocket:mySocket

onPortNumber:12163

atSpeed:28800

withClient:myClient

andExtraHeaders:nil];

Of course, its up to developers to write the methods such that parameters are well named, but I'm happy with how Cocoa methods are named. If I want to do something, sometimes I just guess a method and its parameters, and half the time the method I guessed actually exists! I think this works because the methods are very readable and very memorable, at the cost of some typing speed.

Obj-C, especially used with Cocoa, is a very friendly and easy to use combination that I'm very happy with as a relatively new person to the development world.

Peace,

sam

Also, the bracket syntax is harder to type and edit. If you're typing a chain of calls, you have to either count them ahead of time so that you know how many open brackets to type, or go back and add the open brackets later. With the dot syntax, you just add another dot and keep typing. Likewise, if you have an expression selected and want to use it as a receiver, you have to add text on both sides. Editor support, such as BBEdit's Balance command and Glossary, can help a lot. But I'd like to see an editor that's bracket-savvy in the way that Emacs is for Lisp (which uses lots of parens).

Complete: Coming home from town after having a few drinks at the Brit-Pop party thingy they did at Gromo...