[Hints] C++

[P1raten]

:Hint I:

Here's a few examples of what your allowed to write when writing in C++, so that you wont get any errors.

int awesome; // valid
int Awesome; // valid and distinct from poodle
int AWESOME; // valid and even more distinct
Int really; // invalid -- has to be int, not Int
int doodle_a2 // valid
int _doodlea2; // valid but reserved -- starts with underscore
int 4show; // invalid because starts with a digit
int double; // invalid -- double is a C++ keyword
int begin; // valid -- begin is a Pascal keyword
int __noobs; // valid but reserved – starts with two underscores
int the_awesome_variable_of_all_time; // valid
int shit_tard; // invalid -- no hyphens allowed

:Hint II:

Arrays

"An array is a data form that can hold several values, all of one type. For example, an array can
hold 60 type int values that represent five years of game sales data, 12 short values that represent
the number of days in each month, or 365 float values that indicate your food
expenses for each day of the year. Each value is stored in a separate array element, and the
computer stores all the elements of an array consecutively in memory."

"To create an array, you use a declaration statement. An array declaration should indicate three
things:
• The type of value to be stored in each element
• The name of the array
• The number of elements in the array"

The Array as Compound Type

"An array is called a compound type because it is built from some other type. (C uses the term derived
type, but, because C++ uses the term derived for class relationships, it had to come up with a new
term.) You can’t simply declare that something is an array; it always has to be an array of some particular
type. There is no generalized array type. Instead, there are many specific array types, such as
array of char or array of long. For example, consider this declaration:
float loans[20];
The type for loans is not “array”; rather, it is “array of float.” This emphasizes that the loans array
is built from the float type."

[mgX]

Im very much against the oldschool hungarian type of naming... It was used back in the days, so people would know what type the actual variable was. Usually ppl name constants AS_SOMETHING_STUPID, which looks ridiculous aswell. Ive come to favor the newer type of naming, where one would do:

somethingHere - private members
SomethingHere - public members
_somethingHere - reserved as in, do not touch!

To me it looks much prettier, and with intellisense theres no longer any need for enforcing the hungarian naming. PascalCase ftw

[P1raten]

Im very much against the oldschool hungarian type of naming... It was used back in the days, so people would know what type the actual variable was. Usually ppl name constants AS_SOMETHING_STUPID, which looks ridiculous aswell. Ive come to favor the newer type of naming, where one would do:

somethingHere - private members
SomethingHere - public members
_somethingHere - reserved as in, do not touch!

To me it looks much prettier, and with intellisense theres no longer any need for enforcing the hungarian naming. PascalCase ftw

qft. (o_q)

[mgX]

qft. (o_q)

is it me, or wasnt this topic meant as a debate on variable naming? I believe my input is valid on that. If you meant to go down the hungarian naming road, you barely even covered the basics, not even including prefixes...

[Sounddead]

I usually go with PascalCase/CamelCase because imo it looks nicer and helps me remember which variables are which.

[Spectre90]

Im very much against the oldschool hungarian type of naming... It was used back in the days, so people would know what type the actual variable was. Usually ppl name constants AS_SOMETHING_STUPID, which looks ridiculous aswell. Ive come to favor the newer type of naming, where one would do:

somethingHere - private members
SomethingHere - public members
_somethingHere - reserved as in, do not touch!

To me it looks much prettier, and with intellisense theres no longer any need for enforcing the hungarian naming. PascalCase ftw

While I agree and even use some of this style, IIRC Identifiers with _ at the beginning are reserved and we should not use them in our style/naming conventions as it interferes with the standard.

Although I honestly believe the chances of someone actually causing a conflict by using that style are extremely low, it shouldn't be considered good practice for anyone learning who may not fully understand the implications.