2020-01-01 21:29:24 +01:00
|
|
|
#ifndef BLOCKV_H
|
|
|
|
|
#define BLOCKV_H
|
|
|
|
|
|
2020-07-19 06:21:27 +02:00
|
|
|
#include <SDL.h>
|
2020-01-01 21:29:24 +01:00
|
|
|
#include <string>
|
|
|
|
|
|
|
|
|
|
class blockclass
|
|
|
|
|
{
|
|
|
|
|
public:
|
Explicitly declare void for all void parameter functions (#628)
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.
2021-02-25 23:23:59 +01:00
|
|
|
blockclass(void);
|
|
|
|
|
void clear(void);
|
2020-01-01 21:29:24 +01:00
|
|
|
|
|
|
|
|
void rectset(const int xi, const int yi, const int wi, const int hi);
|
2020-04-04 00:26:19 +02:00
|
|
|
|
|
|
|
|
void setblockcolour(std::string col);
|
2020-01-01 21:29:24 +01:00
|
|
|
public:
|
|
|
|
|
//Fundamentals
|
|
|
|
|
SDL_Rect rect;
|
|
|
|
|
int type;
|
|
|
|
|
int trigger;
|
|
|
|
|
int xp, yp, wp, hp;
|
|
|
|
|
std::string script, prompt;
|
|
|
|
|
int r, g, b;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
#endif /* BLOCKV_H */
|
