Imortis wrote:Can you point me in the right direction?
I think you need to have the right attitude. The desire to keep learning and working at it even when it takes a long time and is difficult. Not trying to be a jerk here, but if you don't know your way around the sources, then yeah, you will have to spend more time looking around the sources. After a while, you learn what things are called and what they do (like functions, data structures, types, #define's). Don't let yourself give up so easily.
To help me find things, I use an editor that lets me open all the sources at once and I use the search function. I also use grep from the command line.
For fbc sources, there is some info on the wiki dev pages. In particular https://www.freebasic.net/wiki/wikka.ph ... FbcModules
is a nice overview.Most efficient way, I think, to get introduced to the compiler is to have a goal in mind (e.g. a bug report) and start tracking it down.
If it is compiler related, then minimally, you should learn how to:
1) build a debug version of fbc
2) use a debugger to trace execution through the compiler as it compiles a source
If it is run time related, then minimally, you should learn how to:
1) build a debug version of rtlib & gfxlib2
2) use a debugger to trace execution through a compiled program and step in to the rtlib & gfxlib2 source
As you work towards your goal, you will learn as you go, tracing through functions and inspecting variables.