mirror of
https://github.com/TerryCavanagh/VVVVVV.git
synced 2024-09-29 17:57:23 +02:00
6a3a1fe147
Apparently in C, if you have `void test();`, it's completely okay to do `test(2);`. The function will take in the argument, but just discard it and throw it away. It's like a trash can, and a rude one at that. If you declare it like `void test(void);`, this is prevented. This is not a problem in C++ - doing `void test();` and `test(2);` is guaranteed to result in a compile error (this also means that right now, at least in all `.cpp` files, nobody is ever calling a void parameter function with arguments and having their arguments be thrown away). However, we may not be using C++ in the future, so I just want to lay down the precedent that if a function takes in no arguments, you must explicitly declare it as such. I would've added `-Wstrict-prototypes`, but it produces an annoying warning message saying it doesn't work in C++ mode if you're compiling in C++ mode. So it can be added later.
52 lines
681 B
C
52 lines
681 B
C
#ifndef MATHGAME_H
|
|
#define MATHGAME_H
|
|
|
|
#include <math.h>
|
|
#include <stdlib.h>
|
|
|
|
//// This header holds Maths functions that emulate the functionality of flash's
|
|
|
|
|
|
//random
|
|
//Returns 0..1
|
|
float inline fRandom(void)
|
|
{
|
|
return ( float(rand()) / float(RAND_MAX)) ;
|
|
}
|
|
|
|
inline int clamp(int x, int a, int b)
|
|
{
|
|
return x < a ? a : (x > b ? b : x);
|
|
}
|
|
|
|
struct point
|
|
{
|
|
int x;
|
|
int y;
|
|
};
|
|
|
|
inline int VVV_min(const int a, const int b)
|
|
{
|
|
if (a < b)
|
|
{
|
|
return a;
|
|
}
|
|
else
|
|
{
|
|
return b;
|
|
}
|
|
}
|
|
|
|
inline int VVV_max(const int a, const int b)
|
|
{
|
|
if (a > b)
|
|
{
|
|
return a;
|
|
}
|
|
else
|
|
{
|
|
return b;
|
|
}
|
|
}
|
|
|
|
#endif /* MATHGAME_H */
|