> Pretty fancy... before long you'll have an all new derived language! That's what it does look like sometimes, but I'd stop short of that. I really just need what in effect are typing aids. The macros are proven so there's no need to type their contents long-handedly. It should be noted though that if you need to be thrifty with memory, using macros, especially those of more than a few lines, a lot can be wasteful. Better to call a routine > While I'm learning assembly I think its probably best to stick with > the bsf STATUS,5 type stuff until it sinks in sufficiently That's fair enough, although it is maybe easier to make mistakes. But even learning the hard way is an education too ;-) Soon enough you'll want to move on from nuts and bolts to writing code as quickly and as conveniently as possible. This could also mean having whole sections of code, like RS232 or maths routines, as library files > is .10 shorthand for d'10'? the manual seems to indicate that .'10' is ok, > and d'10' is acceptable, but says nothing about .10 without the ''s You can find the acceptable types in MPASM Assembler Help under "Radix Types Supported" - Numeric Constants And Radix. They can be mixed any way that makes it easier to understand the routine for example lfsr fsr0,command+0x03 ;source nn_loop movfw indf0 ;test for only numbers xorlw 0x0d ;look for e-o-s Carriage Return bz copy_pho xorlw 0x0d ;no, restore W addlw .255-"9" ;test if number addlw ("9"-"0")+1 skpc goto char_err ;not number incf fsr0l bra nn_loop This is true also for the Watch Window. It can be set to display registers in a number of different formats, such as ASCII, binary, 32-bit etc which allows you to examine registers in a meaningful way > is $ shorthand for PCL (0x02 on the 77)? The argument after the $ is how far the branch or goto is. This is in bytes for the 16F and byte pairs for the 18F, ie a BRA or GOTO on the 18F has to be an even number -- http://www.piclist.com hint: To leave the PICList mailto:piclist-unsubscribe-request@mitvma.mit.edu