Ray Wenderlich Fundamentals Course - Part 4

Here we go! Last chapter of the course for fundamentals. This one is a bit longer so may need two entries. Let's go!

Start Time - 17:39

Compound types - e.g. for tuples. This is about information being bundled together.

Value and reference types - we'll be coming to that!

Functions

func printPass(grade: Int, pass: Int) {
    if grade >= pass {
        print("Your grade score of \(grade) has passed! You passed by \(grade - pass).")
    } else {
        print("Your grade score of \(grade) did not pass!")
    }
}


printPass(grade: 72, pass: 50)

I've elaborated on this a bit. 

OK, difference between parameter and argument. It's called parameter when declared. When called, and providing values, it is an argument! Cool, that does clarify. 

func printHighestGrade(_ grade1: Int, _ grade2: Int) {
    
    print(grade1 > grade2 ? grade1 : grade2)
    
}

printHighestGrade(44, 56)


Good use of the ternary operator above. 

Functions represent tasks or actions. So it is convention to use verbs. Most important thing is staying consistent in the naming. 

*Paused for around 15 mins. 

Mention of type alias. Use of when calling function to create a new type. 

Challenge no problem at all. 

So that's all functions done. 

Finish Time - 18:31 (37 minutes total)

So all functions done. And all good! Will finish off rest of the chapter tomorrow.

Comments

Post a Comment

Popular posts from this blog

Unit Testing Your Code

So, once again I've managed to leave a huge gap between these blogs! The good news is that the Summer Holidays are approaching and there will DEFINITELY be time to code then! So, between now and then, I need regular entries so I can learn what is left in 'Learn to Code in Swift 4', then make a new plan for how to take my knowledge forward. Anyway, the next chapter is all about 'Unit Testing', which sounds interesting! The three facets of a successful app are: well designed, stable and easily adaptable to change. Apparently, many app developers do not test their code properly; the most effective approach is to test one line at a time, after writing. That makes sense! So 'Unit Testing' is a method to test individual 'units' - usually methods. Having read over the next few pages, a lot of this seems unnecessary at present; I'm still getting used to writing codes let alone testing and debugging! This is something that I can revisit when I have ha...
Read more

Functions (part 1)

So I am now on to the next course! This one is all to do with functions. These I remember fairly well from before but, as I've found, it's not so much the concept but the application of it that I find trickier. We'll see how it goes! What is a Function? Pasan explains this through the example of making coffee - a series of steps for a very specific task. When needing coffee, the sae series of steps are carried out! DRY - Don't Repeat Yourself! So, rather than going through the steps of something e.g. making coffee every time, we can just call up the function of making coffee. A coffee maker carries out all of these steps so you don't actually have to do each one. It is a 'self contained block of code that carries out a specific task'. Functions in Code let length = 12 let width = 10 let area = length * width I think the point that Pasan is going to make here is that it is cumbersome to keep changing values or doing this each t...
Read more

Introduction to Optionals (Part 1)

Yes - one day's break, but not because I needed or wanted one! I was genuinely to busy for any Swift yesterday, so it feels good to be back! Having written entries each day for a week, I missed it! Enumerations are done for now; Optionals are next... The Absence of Data I think the idea of this is 'nil' - nothing! Pasan explains 'safe' code, where crashes need to be avoided. Optionals are new - since the inception of Swift I believe.  struct Person {          let firstName: String     let middleName: String ?     let lastName: String } I've pre-empted the ? - to make middleName an optional. If I didn't have this, then an error would be caused - you can't input nil. The question mark - making it an optional - means that nil CAN be used. So it means it may have a value OR may be nil. They do seem cumbersome, but apparently they are powerful and useful! In the example above, it means that it is a string and ma...
Read more