From: Philipp Rumpf <prumpf@inwestnet.de>
To: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Assembly Language Changes
Date: Wed, 15 Mar 2000 22:16:47 +0100 [thread overview]
Message-ID: <20000315221647.G673@abacus.local> (raw)
In-Reply-To: <20000312152353.E5281@abacus.local>; from prumpf@inwestnet.de on Sun, Mar 12, 2000 at 03:23:53PM +0100
I haven't received any negative comments about the proposed changes yet,
and think the following changes should become effective soon:
> - Labels should always use ':'
> - mnemonics in the first column should be interpreted normally.
> - register names should always start with '%', not be specified by an
> integer
> - ';' should be used rather than '!' to separate multiple statements
> on the same line
- '!' replaces ';' as the line comment character
I don't think a line comment character should be necessary for new code -
C comments (thats /* comment */, not // comment\n) work fine.
So, still no objections ?
Philipp Rumpf
prev parent reply other threads:[~2000-03-15 22:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-12 14:23 [parisc-linux] Assembly Language Changes Philipp Rumpf
2000-03-14 14:54 ` Sam Creasey
2000-03-14 14:58 ` Philipp Rumpf
2000-03-15 21:16 ` Philipp Rumpf [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20000315221647.G673@abacus.local \
--to=prumpf@inwestnet.de \
--cc=parisc-linux@thepuffingroup.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox