-Alloc [[]Init] vs. New

Any instance. But now that you asked, I see that the intiialization can be done wherever it's needed, which was the same discussion that we already were having.

So I guess I'm trying to find out where an application starts. Does the .main document point to the first starting meathod? Or do you code the first meathod in .main? Do you have to decalre, impliment, allocate and initialize

-(void) main { } class and function?

Thanks for the reply. It's Mac OS here.

Either way, I still don't understand how you know where the application will start? It loads in all the declarations and implimentations, and then what? Where does the computer go from there and by what cause?

I'll have to think about this a little, if implemenation is all that's needed to get the application to the desired state, and ready from the next change of state.

Provided at least one of the implimentations initializes a method?

Well, I mean if the implementation impliments all the starting values of any methods that are initialized in the implimentation (Is that what happens?),

then all the values and all the states that are in the initialized parts of the implimentation code will be set, whether values for the graphic, or values for variables, etc, and the implimentation itslelf will then be waiting, after implementation, for the next signal from the user which will create the dominoe-switching effect throughout the implemenatation code that will cause the computer and all the declared values and memory/buffer locations to contain the new values, or change of state for the application?

In other words, the implementation is actually the code read in its entirety, and not sequentially, necessarily.

Or, there's no 'starting point', but the entire implementation is the starting point.

OK, thanks again for the replies. It appears that initialization itself is a rather invovled topic, where there are many important considerations to make regarding what to intialize, when and how, (and also what to allocate, when and how).

So the question about the [[* alloc] init] message that I started with on this thread is actually the beginning of the topic, rather than the end of it!

It makes sense to me that entire application runs as a continuous loop, and now also that makes it clear why intitialization is a more complicated topic than just sending one message.

I'm not having much trouble with the other aspects of development, so far, and I don't see where more ability with a more linear execution is really going to help me overcome the need to learn more about initialization. So far teh topic doesn't seem particularly friendly, but as smooth as discovering the other parts of Cocoa development have gone, I'm either over-estimating the difficulty or rightly in for a little more work at reading, studying on the topic.

I'm keeping your suggestion front and center, though, as launching a C document is clearly the best path to take when developing methods. Can I copy and paste Core Framework meathods into C documents to test them out?