Okay I'm about to dive into this chapter about Data Types and Expressions. Back when I was trying Obj-c about 7 months ago I got to this chapter and it was pretty hard for me to grasp these concepts. So do you guys have any tips for me?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iOS Data Types and Expressions.
- Thread starter RobertD63
- Start date
- Sort by reaction score
1. Ask specific questions.
1b. If you're asking a question about something in a specific book, give the author, title, and version of the book. If the problem is with a specific passage or sentence in the book, then quote that specific passage or sentence, rather than paraphrasing it.
2. Don't expect anyone to remember what you did (or posted about) 6 months ago. Or one month ago. Or even one week ago, if it's on a high-traffic forum.
3. http://www.mikeash.com/getting_answers.html
1. I was asking for any kind of tips that helped you guys learn Data Types and Expressions.
1b. I dont have any problems with the book, actually I love it.
2. I wasn't asking anyone to "remember" what I did or posted back then. I actually said nothing about that, I was just giving a backlog that i've tried to learn it before and it was extremely hard for me.
3. Thank you for being so kind...
So to be more specific I was wondering when you guys learned how did you get through this?
Everyone is different. Some people understand data types and expressions right away. Other people have difficulty, but with different things. If you don't explain what you found hard, or why you stopped before, there really aren't any tips other than the ones I already gave.
I wasn't suggesting the book was bad (or good). I was simply pointing out that you hadn't identified the book, so there's no way for anyone else to tell you whether the chapter on data types and expressions might be harder or easier to understand than some other book. There's also no way to suggest a complementary book that might give better explanations in this case. You also didn't explain why you found the explanations in the book hard, whether it's lack of background, unfamiliar terms, or whatever.
One example of a difficulty: a guy I worked with was learning C. He came from a mathematics background, so already understood arithmetic expressions, complex calculations, iterative algorithms, number theory, etc. but had never learned any programming language. In one of his programs, he declared some variables as type 'float', then used them as subscripts for C arrays. This didn't work. When he asked me why, I told him that subscripts have to be integers. He assured me they were in fact integers, and sure enough, the values of the variables were integers (0.0, 1.0, 4.0, etc.). I then explained to him that it didn't just have to be an integer number, but the type had to be an integer type. That lead into an explanation of binary numeric representations, especially the difference between the integer types and the floating-point types. He had a specific difficulty (float types used as array subscripts), that took a specific explanation to resolve (numeric representations).
I wasn't suggesting the book was bad (or good). I was simply pointing out that you hadn't identified the book, so there's no way for anyone else to tell you whether the chapter on data types and expressions might be harder or easier to understand than some other book. There's also no way to suggest a complementary book that might give better explanations in this case. You also didn't explain why you found the explanations in the book hard, whether it's lack of background, unfamiliar terms, or whatever.
One example of a difficulty: a guy I worked with was learning C. He came from a mathematics background, so already understood arithmetic expressions, complex calculations, iterative algorithms, number theory, etc. but had never learned any programming language. In one of his programs, he declared some variables as type 'float', then used them as subscripts for C arrays. This didn't work. When he asked me why, I told him that subscripts have to be integers. He assured me they were in fact integers, and sure enough, the values of the variables were integers (0.0, 1.0, 4.0, etc.). I then explained to him that it didn't just have to be an integer number, but the type had to be an integer type. That lead into an explanation of binary numeric representations, especially the difference between the integer types and the floating-point types. He had a specific difficulty (float types used as array subscripts), that took a specific explanation to resolve (numeric representations).
Ah okay makes plenty sense now, sorry bout that. The book I'm reading is
Programming in Objective-C 2.0 by Stephen G. Kochan. What I dont understand is here:
So does this mean that any thing that I typed out in lets say NSLog is a constant character string object?
No, not any thing, only the things that are string objects.
Not everything is a string.
Not everything is an object, either.
Examples:
Code:
NSLog( @"%d", 27 );
Code:
NSLog( @"%f", 355.0/113.0 );
Code:
NSLog( @"%c %c", '6', 'c'+1 );
Code:
NSLog( @"%s", "xyzzy" );
Code:
NSLog( @"%@", @"foo" );