From: Nemo Nusquam <cym224@gmail.com>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Design of the AT&T assembly syntax
Date: Mon, 28 Oct 2019 20:31:16 -0400 [thread overview]
Message-ID: <5623d077-218b-4b15-ae62-8b84ab4bbfae@gmail.com> (raw)
In-Reply-To: <4a3383f9-473b-430c-8b91-6324a2793437@www.fastmail.com>
On 10/28/19 17:06, Seth Morabito wrote:
>>
>> Thanks for pointing this out, I think it's a really interesting read.
>>
>> [...] because I actually like and prefer AT&T syntax.
+1
> I think most of the other developers I know find my attitude to be abhorrent :)
>
> -Seth
next prev parent reply other threads:[~2019-10-29 0:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 20:14 Robert Clausecker
2019-10-28 21:06 ` Seth Morabito
2019-10-29 0:31 ` Nemo Nusquam [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-29 14:38 Alexander Voropay
2019-10-28 21:48 Alexander Voropay
2019-10-28 21:59 ` Robert Clausecker
2019-10-28 20:07 Robert Clausecker
2019-10-28 22:08 ` Warner Losh
2019-10-28 22:24 ` Robert Clausecker
2019-10-28 22:29 ` Warner Losh
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=5623d077-218b-4b15-ae62-8b84ab4bbfae@gmail.com \
--to=cym224@gmail.com \
--cc=tuhs@minnie.tuhs.org \
/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;
as well as URLs for NNTP newsgroup(s).