mirror of
https://github.com/TerryCavanagh/VVVVVV.git
synced 2025-01-11 03:19:46 +01: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.
35 lines
495 B
C++
35 lines
495 B
C++
#ifndef TOWER_H
|
|
#define TOWER_H
|
|
|
|
class towerclass
|
|
{
|
|
public:
|
|
towerclass(void);
|
|
|
|
int backat(int xp, int yp, int yoff);
|
|
|
|
int at(int xp, int yp, int yoff);
|
|
|
|
int miniat(int xp, int yp, int yoff);
|
|
|
|
void loadminitower1(void);
|
|
|
|
void loadminitower2(void);
|
|
|
|
void loadbackground(void);
|
|
|
|
void loadmap(void);
|
|
|
|
short back[40 * 120];
|
|
short contents[40 * 700];
|
|
short minitower[40 * 100];
|
|
int vmult[40 * 700];
|
|
|
|
bool minitowermode;
|
|
};
|
|
|
|
|
|
|
|
|
|
|
|
#endif /* TOWER_H */
|