thanks for considering. JoseLB did some work http://www.mikroe.com/forum/viewtopic.php?t=9919 , which does much more than I imagined, but the straight text substitution of "<<macro>>" tags with previously defined ones before compilation would already do. Of course I see the difficulty with the code ...

Nice work you did there! On the definition part, I could settle witch much less, just writing a definition file, as the .inc files of mplab. Where I have a problem, and that's where me comes in, is with compilation. I am used to recompile everey 3-4 lines I write, download and check my code. Therefo...

for code readability, to optimize code for speed and to create my own "RTOS" functions, i need inline procedures (macro definitions with arguments passing).
I may be off the standard track, but this allows me to write my own device drivers efficiently.

OK, that unfortunately means "not yet".
Being used to write my HW drivers myself, this ties me up pretty much.

Thanks for the reply!

Your example works fine, as long as you do not move an I/O bit to a different port, which easily happens at layout or re-layout time...
I'm really eagerly waiting for bit pointers to be implemented

Hi! I am new to mP, but with long MpLab Assembly experience. When handling SFR, I would like to access bits symbolically, e.g. T4IF := 0; // clear Timer 4 interrupt flag rather than IFS1.5 := 0; // clear Timer 4 interrupt flag It is a matter of readability and portability of the code. Is there a way...