[Ibson]

Ah! I started a project a few months ago, and originally thought that it would be a small project, so (in my lack of foresight) I named my classes willy-nilly. Now, many classes will be public, along with notifications, constants, etc. There are about 50 classes in my project. I'm just wondering whether people think it is worth the effort to go back and prefix my class names/notifications/whatever?

[Diggory Laycock]

Originally posted by Ibson:
Ah! I started a project a few months ago, and originally thought that it would be a small project, so (in my lack of foresight) I named my classes willy-nilly. Now, many classes will be public, along with notifications, constants, etc. There are about 50 classes in my project. I'm just wondering whether people think it is worth the effort to go back and prefix my class names/notifications/whatever?

If they are going to be public - absolutely.

[Ibson]

Should I bother prefixing my private classes? Also, would one tend to use a company-specific prefix or an application-specific prefix (I've seen examples of both).

*sigh* I'll start now then...

[Angus_D]

If they're specific to your app, use an app-specific prefix. If you want them to be reusable in other applications, you can use a company or person-specific (if you're just working along) prefix.

[Chuckit]

Originally posted by Ibson:
Should I bother prefixing my private classes? Also, would one tend to use a company-specific prefix or an application-specific prefix (I've seen examples of both).

*sigh* I'll start now then...

Couldn't you just use Project Builder's built-in find-and-replace ability? It seems like it wouldn't be that hard with that.

[LordJavac]

Isn't there some way to create a namespace around our classes?! Like a package in Java or namespaces in C++. This is the only thing I dislike about Objective C.

[Ibson]

Originally posted by LordJavac:
Isn't there some way to create a namespace around our classes?! Like a package in Java or namespaces in C++. This is the only thing I dislike about Objective C.

Unfortunately, no. The Objective-C runtime has a single, flat namespace per process for all exported symbols: such as global variables, class names, nonstatic functions, and categories. Protocols have a separate global name space of their own.

[zorn]

I *think* two level namespases were intro-ed in 10.1 although I've never really tried it...

http://developer.apple.com/techpubs/...amespaces.html

Maybe it's language specific, meaning for use in Obj-C++ only??