“EXC_BAD_ACCESS” in Xcode?

You really left out the essentials here (the actual assignment) and you are using iWeight instead of nWeight (typo i'm sure) in your example. Just make sure when you assign the NSNumber you actually assign it an NSNumber object not a literal (ex. NWeight = 5).

And also make sure you use the property self. NWeight = NSNumber numberWithInt:5.

You really left out the essentials here (the actual assignment) and you are using iWeight instead of nWeight (typo i'm sure) in your example. Just make sure when you assign the NSNumber you actually assign it an NSNumber object not a literal (ex. NWeight = 5).

And also make sure you use the property. Self. NWeight = NSNumber numberWithInt:5.

I assume you mean nWieght on that NSLog line -- if not update with more code. What has happened to nWieght in its lifetime? Does it have a value -- was that value released and dealloced?

The easiest way to tell is to turn on Zombies with the the Zombies instrument. This will set each object to not deallocate when it is fully released, and turn it into a zombie object instead. If you try to send a message to a zombie, it will complain loudly in the Console, and you get a much better indication of what you did wrong.

There are many other ways to cause EXC_BAD_ACCESS, which I documented here: loufranco.com/blog/files/Understanding-E....

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.