Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!microsoft!alonzo From: alonzo@microsoft.UUCP (Alonzo GARIEPY) Newsgroups: comp.sys.handhelds Subject: Re: (long) Re: SAD - Saturn Disassembler Beta 1.01 Message-ID: <57550@microsoft.UUCP> Date: 19 Sep 90 02:24:47 GMT References: <10712@life.ai.mit.edu> <57448@microsoft.UUCP> <10753@life.ai.mit.edu> <57461@microsoft.UUCP> Reply-To: alonzo@microsoft.UUCP (Alonzo GARIEPY) Organization: Microsoft Corp., Redmond WA Lines: 28 esmith@goofy.apple.com (Eric Smith) writes: | alonzo@microsoft.UUCP (Alonzo GARIEPY) writes: || The ideas was that ALL numbers || in hex have a # in front. That makes life much easier for the lexical || front end to understand what it is getting. |How about using "$" to indicate hex? Many assemblers for 65xx and 68xx |processors do that. Or suffix an "h", "d", "o", or "b" for hex, decimal, |octal, or binary, as most 808x and x86 assmeblers use. Or (less preferred) |how about "0x" as C uses? Anything but "#", please! Any good reasons? Because assembler and RPL will eventually be integrated, it makes sense to merge their basic syntax. Actually, the more I think about this the better I like it. || The vertical bar should be reserved for C-like bitwise operations. || And I realized that I would prefer to use quotes for string literals. || How about enclosing nonstandard symbols in < and >, and you can think || of them as part of the symbol. I would prefer that such symbols were || alphabetized by their second character, however :-). One's needs are often constrained by harsh reality, but I admit my experience is similar to your own. The problem is the large database of disassembly symbols that are intended to be self documenting. I do think some extension is in order. Syntax needs more thought. Perhaps various literals and RPL objects should be handled with explicit lexical functions, and we can use quotes for symbols. Alonzo