🚀 go-pugleaf

Goran Larsson writes
: > int ISomefunction(int iSomeArg)
: > {
: > int iRetVal = 0;
:       ^
: Why are you trying to make C look like FORTRAN?

: What a crazy world - some programmers try to hide data types to make
: updates easier - some try to encode data types in variable names and
: function names to make updates a nightmare...

The intention is not to make updates a nightmare but to avoid problems
when several programmers are working together.  Knowing the argument
types a function needs and the type of variables you are using to invoke
the function is important.  You could also debug faster (e.g. piTest = piFirst;
is functionally ok as it assigns a pointer to another of the same kind).
In addition, it helps users avoid mistakes like Test.a when Test->a
is required (use pTest->a, the p should be in front of the variable in
order to use ->).

If a variable is changed to another type, a simple global/local change doesn't
cause too much trouble as most editors nowdays can do it automatically.  I
believe it helps more than what you think.  You certainly don't have to follow
any variable naming convention but please don't critize people who do.