From: cinap_lenrek@felloff.net
To: 9fans@9fans.net
Subject: Re: [9fans] kenc vlong <asop> double
Date: Mon, 14 Sep 2015 14:59:57 +0200 [thread overview]
Message-ID: <ae2ef0bf128acb32cabedca74e752cac@felloff.net> (raw)
In-Reply-To: <CAOw7k5h8pqCVQrH_Gtqj=-rVmBEWBAFDpJrht6N__vPw6wOB1g@mail.gmail.com>
is there any reason to handle the <asop> as single operations instead
of breaking it down into separate <as> and <op> operations? that is,
is (a <op>= b) always equivalent to (a = a <op> b)?
--
cinap
next prev parent reply other threads:[~2015-09-14 12:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-13 8:09 cinap_lenrek
2015-09-13 13:45 ` erik quanstrom
2015-09-13 14:23 ` cinap_lenrek
2015-09-13 15:54 ` Charles Forsyth
2015-09-13 17:10 ` Charles Forsyth
2015-09-13 18:01 ` cinap_lenrek
2015-09-13 18:21 ` erik quanstrom
2015-09-13 18:31 ` Charles Forsyth
2015-09-13 18:28 ` erik quanstrom
2015-09-13 18:33 ` Charles Forsyth
2015-09-13 18:46 ` cinap_lenrek
2015-09-13 18:55 ` Charles Forsyth
2015-09-14 12:32 ` Charles Forsyth
2015-09-14 12:59 ` cinap_lenrek [this message]
2015-09-14 13:18 ` Charles Forsyth
2015-09-14 13:59 ` Charles Forsyth
2015-09-14 14:50 ` cinap_lenrek
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=ae2ef0bf128acb32cabedca74e752cac@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9fans@9fans.net \
/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).