On Mon, Sep 14, 2009 at 8:28 PM, Olin Lathrop w= rote: > Manu Abraham wrote: >> Sorry, that it stirred up such a long discussion on this list. I >> didn't want to add more fuel to this long discussion, but there are >> reasons why generally spaces are avoided in code maintenance. > > I don't think it's "generally" done one way or another. > >> Some years following a certain coding style puts you into that style >> alone. It just got me surprised when someone said use spaces instead >> of tabs. > > Again, we don't care what is in the code on your own machine. =A0The poin= t is > you need to remove tabs before posting it publicly. > >> So, i guess the question of spaces arrives from a broken >> e-mail client. > > Wow, that's so arrogant, especially after we've explained various technic= al > reasons tabs cause trouble, and considering you're the one coming here fo= r a > favor. With all due respect, quoting yourself: On Sat, Sep 12, 2009 at 9:54 PM, Olin Lathrop w= rote: > Manu Abraham wrote: >> isr >> movwf fsr_tmp -- snip-- >> >> ; actual ISR >> bcf INTCON, INTF >> bsf flags, LEDBIT >> >> ; restore registers >> movf fsr_tmp, w >> movwf FSR >> movf pclath_tmp, w >> movwf PCLATH >> swapf status_tmp, w ; set bank to original >> movwf STATUS ; restore >> swapf w_tmp, f ; swap tmp >> swapf w_tmp, w ; swap tmp -> w >> >> retfie > > How did this mess ever assemble? Opcodes are not allowed in column 1 else > the assembler interprets them as labels. I do respect the list posting rules, it's different for every list. But that said, If i send something from my email client and you receive it differently in your email client, while some others also state that it looks fine, don't you think that, err.. your email client is broken ? -- = http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist