EvilSOB, thank you for your kind explanations. You're opening a further part of a door to new fields in programming to me!
I looked for the first time into the header files of Lite-C like atypes.h, now.
// use for the lite-C compiler
typedef struct C_LINK {
long index; // index number of the object (handle)
struct C_LINK *next; // pointer to next object
char *name; // pointer to name of object (if any)
} C_LINK; // object header
typedef byte* EVENT; // just a pointer to a machine code function
typedef struct STRING {
C_LINK link;
char *chars; // pointer to null terminated string
long length; // allocated length of string
long flags; // see STRF_... above
byte pad[PAD_STRING];
} STRING;
typedef struct SOUND {
C_LINK link;
long length;
byte *buffer;
long type; // 2 = WAV, 5 = OGG
} SOUND;
This could be a way to get an idea how to organize my own code, when looking at the code of the engine that I know quite closely from the wdl site.
@ Joozey:
Yeah, I already recognized that. Very much appreciated. I'll definitely have a closer look into that soon!
Explanations like that are very appreciated!
