On Wed, Jul 27, 2011 at 12:45:58PM -0600, Doug McNutt wrote: > > I even have a preset resource file into which I can redirect a data > fork that is an assembly language listing for a 68HC11 microprocessor. > Variable width tabs are really nice for that. I can even word wrap > comments into new lines that begin at the rightmost tab.
Nice, but most assemblers are soft on the location of the opcode field so long as there is at least one whitespace leading in. Two tabs, or any number of spaces is accepted. Followed by at least one whitespace to the arguments, and comments start at first semicolon or after legal arguments. Has been a while but believe I last used 2 tabs at 8 spaces for the label field, one for opcode, one more to the arguments, and 2 more to comments. In in my old age I've come to prefer hard spaces so that nobody comes along and messes up my formatting just because they used a different tab value. -- David Kelly N4HHE, [email protected] ======================================================================== Whom computers would destroy, they must first drive mad. -- You received this message because you are subscribed to the "BBEdit Talk" discussion group on Google Groups. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at <http://groups.google.com/group/bbedit?hl=en> If you have a feature request or would like to report a problem, please email "[email protected]" rather than posting to the group. Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
