<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>On 5-Apr-08, at 10:24 AM, Gerd Knops wrote:<br><blockquote type="cite"><div><br>On Apr 5, 2008, at 8:36 AM, Edward K. Chew wrote:<br><blockquote type="cite">On 5-Apr-08, at 9:08 AM, Luke Daley wrote:<br></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Hi Ted,<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">There is a page in the manual on this.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="http://macromates.com/textmate/manual/language_grammars#naming_conventions">http://macromates.com/textmate/manual/language_grammars#naming_conventions</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">LD.<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Thanks, Luke. I have looked at that page, and the existing conventions seem to cater mostly to compiled or scripted languages. Assembly languages are certainly varied, but do tend to share some common elements that could use their own naming scheme.<br></blockquote><blockquote type="cite"><br></blockquote>I had the same experience when adding a language definition for SX uC assembler. And if you make up your own, downside is that you will also need to add syntax highlighting to all themes you use.<br><br>Since I am not intending of making mine public, I kind of went backwards: In the preferences I looked how the various scopes were highlighted, and picked based on that, adding ".assembler" to all. I still had to make up a few to get the highlighting balanced. I am sure the language police would object strongly, but it works fine for my purposes.<br></div></blockquote></div><br><div>Okay, well it sounds like there is no real consensus on assembly. I guess I'll stick with what I've got, then, which currently looks like this:</div><div><br></div><div><b>meta.preprocessor.directive.assembly.Asm9600</b><b>2</b>: assembler directives (e.g. dcb: define byte-level storage)</div><div><b>meta.preprocessor.function.assembly.Asm9600</b><b>2</b>: functions evaluated at assemble-time (e.g. @cvs: convert memory space)</div><div><b>k</b><b>eyword.other.opcode.assembly.Asm96002</b>: processor instructions (e.g. bclr: test and clear one bit)</div><div><b>variable.language.register.assembly.Asm96002</b>: internal registers and their sub-fields</div><div><b>constant.numeric.assembly.Asm96002</b></div><div><b>string.quoted.single.assembly.Asm96002</b></div><div><b>comment.line.assembly.Asm96002</b></div><div><br></div><div>Here is an example of how it looks in the Mac Classic theme:</div><div><br></div><div><img height="352" width="572" apple-width="yes" apple-height="yes" src="cid:E15D73BA-71B9-45A7-8FDD-F9CB17F8CF12@ekc.homeip.net"></div><div><br></div><div><div>(Aside: I couldn't find any way to copy or save text with the formatting preserved and had to resort to a screen dump. I guess I'll have to add rtf export to my wish list, along with multi-window projects, split views, and print selection.)</div><div><br></div></div><div>I have yet to decide what (if anything) to do with user-defined symbols. Should I try to distinguish between equates (constants), functions, and storage variables? That could be difficult. Maybe I'll cop out and come up with something generic like "label" that covers everything.</div><div><br></div><div>-Ted</div><div><br></div></body></html>