More Dirty Coding Tricks from Game Developers (2010)

Re:More Dirty Coding Tricks from Game Developers (2010) by trashcan on Sunday August 02, 2015 @07:33PM (#9992946)

If you make a function that accepts an unsigned int, and then you try to pass in a const unsigned int, you will need to either typecast it, make a new function, or change the function to only accept const unsigned ints.

Although it's been a long time since I coded in C/C++, correct me if I'm wrong.

[ Parent | on HN ]

Re:More Dirty Coding Tricks from Game Developers (2010) by StephanTLavavej on Sunday August 02, 2015 @08:00PM (#9993034)

You're incorrect, for C89 through C++17. I'd recommend not making statements about languages you've forgotten.

In the C++ Working Paper, the Standardese is N4527 5.2.2 [expr.call]/4 "When a function is called, each parameter (8.3.5) shall be initialized (8.5, 12.8, 12.1) with its corresponding argument." followed by 8.5 [dcl.init] where /17.8 has a nice example:

"Note: An expression of type "cv1 T" can initialize an object of type "cv2 T" independently of the cv-qualifiers cv1 and cv2. int a; const int b = a; int c = b;"

(A "cv-qualifier" is const or volatile; they behave similarly in many contexts, hence the collective terminology for convenience.)

[ Parent | on HN ]

Re:More Dirty Coding Tricks from Game Developers (2010) by trashcan on Monday August 03, 2015 @12:22PM (#9997307)

I stand corrected, thank you.

[ Parent | on HN ]

Re:More Dirty Coding Tricks from Game Developers (2010) by Joky on Sunday August 02, 2015 @07:48PM (#9993000)

That sounds completely wrong, unless the function takes a reference to the unsigned int.

[ Parent | on HN ]