Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Unity 4.x Game Development by Example: Beginner's Guide

You're reading from   Unity 4.x Game Development by Example: Beginner's Guide A seat-of-your-pants manual for building fun, groovy little games quickly with Unity 4.x

Arrow left icon
Product type Paperback
Published in Dec 2013
Publisher Packt
ISBN-13 9781849695268
Length 572 pages
Edition 3rd Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Ryan Henson Creighton Ryan Henson Creighton
Author Profile Icon Ryan Henson Creighton
Ryan Henson Creighton
Arrow right icon
View More author details
Toc

Table of Contents (22) Chapters Close

Unity 4.x Game Development by Example Beginner's Guide
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
1. That's One Fancy Hammer! FREE CHAPTER 2. Let's Start with the Sky 3. Game #1 – Ticker Taker 4. Code Comfort 5. Game #2 – Robot Repair 6. Game #2 – Robot Repair Part 2 7. Don't Be a Clock Blocker 8. Hearty Har Har 9. Game #3 – The Break-Up 10. Game #3 – The Break-Up Part 2 11. Game #4 – Shoot the Moon 12. Game #5 – Kisses 'n' Hugs 13. AI Programming and World Domination 14. Action! Appendix Index

What exactly is "this"?


Did the this.img = img; line trip you up? Here's what's going on with that.

The Card class has an instance variable called img. We're also passing an argument to its constructor function with the exact same name, img. If we simply wrote img = img;, that means we'd be setting the value of the argument to the value of the argument. Hunh! That's not quite what we're after.

By specifying this.img = img;, we're saying that we want the img variable attached to this, the Card class, to have the same value as the argument called img.

It's a smidge confusing, I'll admit. So, why not just call the argument something different? You absolutely could! We did it this way because it's very common to see variables passed to the constructor function with the same name as the instance variables in the class. You may as well encounter it here with a full explanation, than come across it in the wild and let it gnaw your leg off.

Here's one more look at another, completely imaginary class...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image