Where should I discuss SD/MMC FAT issues?

[mister_e]

If _Variable is a CONSTANT, it will work indeed. You can still declare it on asm level

@MyVar=.30

and later call the macro

NOP?C MyVar+10

[skimask]

If _Variable is a CONSTANT, it will work indeed.

That's what I meant...a CONSTANT...
I think this little tidbit is going to save me a bunch of typing soon...

[mister_e]

In this case, it could be better to change it too.

ASM
NOP?C   macro Cin
    local a
a=0
    while a<(Cin+MyByte)
        nop
a++=1
        endw
    endm
ENDASM

and at the top of your code you define MyByte like

@MyByte=.10 ; your value.. whatever

[JD123]

When you first typed "=.30", I thought the decimal and the zero were a type-o. Then I see you used "=.10". It's been a long time (close to 10 years ago) that I've been through the MPASM manual, and I can still go back and read it, but can you explain the "=.30" and "=.10" for defining 3 and 1? I would have thought it would just be "=3" or "=1".

Thanks for taking your time to explain all this to us.

[mister_e]

It's just a MPASM naming convention. Depending the current MPASM radix setting
@a=10
@B=30
Those above could be considered as decimal or hexa.

Let's open a PBP .INC file, let's say 16F628.inc, you'll discover...

    else
        LIST
        LIST p = 16F628, r = dec, w = -302
        INCLUDE "P16F628.INC"   ; MPASM  Header
        ;__config _XT_OSC & _WDT_ON & _PWRTE_ON & _MCLRE_ON & _LVP_OFF & _CP_OFF
        NOLIST
    endif
        LIST

so every value should be considered as decimal using PBP.

MPASM naming convention
.10 or d'10' will always be considered as 10 decimal whatever your Radix setting is.. kinda safe way to write things.

[JD123]

Thanks Mr.E. Now that you mentioned it, I remember dealing with the radix before, but never much explored it many uses. Again, that was a long time ago... and I've had several beers since then.

[mister_e]

oh... think we ALL had few beer... in case you're thirsty