For another project i need to know if and where a LCD ist connected. So, i wrote this little program.
Works nice, but while playing around i find one curious thing.
By mistake i commented the #include <lowlevel\lcd.h> line off. But Compiling was done without error.
Until now i thought that this include is a MUST. Isn't it?</lowlevel\lcd.h>
Any of the following lowlevel\files are now loaded automatically. Now, the compile does not use the contents of one these files until you make a call to something in a specific file. That way the code is still very small.
LOWLEVEL.DAT
'List of files in lowlevel\ to include by defaultpicas.ha-d.hpwm.hrs232.heeprom.hsound.hstdbasic.h7segment.hlcd.hps2.htimer.hsystem.hhwspi.hkeypad.hrandom.hstring.husart.hi2c.hhwi2c.hhwi2c2.hpwm16.hsaf.hhef.hspisram.h
The updated compiler report now shows the number of subs/functions/macros available to a specific program. In your example the total number of subs/functions/macro is 481 but you only use 20 system and 4 that you wrote.
For another project i need to know if and where a LCD ist connected. So, i wrote this little program.
Works nice, but while playing around i find one curious thing.
By mistake i commented the #include <lowlevel\lcd.h> line off. But Compiling was done without error.
Until now i thought that this include is a MUST. Isn't it?</lowlevel\lcd.h>
Thank you!
Nice addition!
Any of the following lowlevel\files are now loaded automatically. Now, the compile does not use the contents of one these files until you make a call to something in a specific file. That way the code is still very small.
LOWLEVEL.DAT
The updated compiler report now shows the number of subs/functions/macros available to a specific program. In your example the total number of subs/functions/macro is 481 but you only use 20 system and 4 that you wrote.
Things are slightly different for GLCD.H... but the same general rule applies to minimise the number of library files compiled.