unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Heike C. Zimmerer" <nospam07q1@gmx.net>
To: emacs-devel@gnu.org
Subject: Re: gas-mode.el - Comments welcome
Date: Thu, 31 May 2007 00:18:59 +0200	[thread overview]
Message-ID: <f3ktpo$vvt$1@sea.gmane.org> (raw)
In-Reply-To: 20070531.032349.202076025.jet@gyve.org

Masatake YAMATO <jet@gyve.org> writes:

> Which architecture are you targeting on? i386?

It is not bound to a specific architecture (there are just too many of
them).  Checking of opcodes or even arguments is IMHO better done by
the assembler.  However, it would be no big deal to highlight specific
opcodes (the code is already there and used to recognize asm
directives) or even to check for the correct number of arguments (the
current parser returns the number of arguments).

I've postponed this idea, since I feel it wouldn't buy much for me.
Once you're accustomed to the instruction set (and I've seen a lot of
exotic ones), getting opcode and number of arguments correct is not
something that IMHO justifies another level of highlighting (I don't
think the more's the better when it comes to it).

I see that it might, however, be a coding aid for the occasional
programmer and for beginners, so if there's enough interest in it, it
can be done, preferably by reading the instruction set from some
external configuration file.

For now, we should stick with the present features and make sure they
work rock solid.

> gdb-ui.el could show disassembled code. If gas-mode can supports
> font-locking well on multiple architectures' assembly code, 
> gas-mode's font-locking code can be applied to gdb-ui.el.

That would be no big deal.  gas-mode can parse any standard assembler
line and return its syntactic fields, including positional
information.  Let's focus on that later.

- Heike

  reply	other threads:[~2007-05-30 22:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-30 14:43 gas-mode.el - Comments welcome Heike C. Zimmerer
2007-05-30 18:23 ` Masatake YAMATO
2007-05-30 22:18   ` Heike C. Zimmerer [this message]
2007-05-31  4:11     ` Masatake YAMATO
2007-05-30 23:05 ` Stefan Monnier
2007-05-31  7:37   ` Heike C. Zimmerer
2007-05-31  9:07     ` David Kastrup
2007-05-31  9:28       ` Heike C. Zimmerer
2007-05-31 17:07     ` Stefan Monnier
2007-06-01  9:18 ` Johan Bockgård
2007-06-01 13:09   ` Heike C. Zimmerer
2008-07-22 19:27 ` Dan Nicolaescu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='f3ktpo$vvt$1@sea.gmane.org' \
    --to=nospam07q1@gmx.net \
    --cc=emacs-devel@gnu.org \
    --cc=hcz@hczim.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).