Cleanup regset >> about x64asm HOT 3 CLOSED

On the other hand, others using x64asm may want this functionality, and it's pretty nice being able to use the stream operators. Do you think it makes sense to move some of the logic here? The current logic in STOKE is better.

from x64asm.

I don't know if I have a good answer for that.

Way back when I had a ostream overload for the reg_set in x64asm, but I
eventually moved it out to stoke. The rationale was that all the printing
methods in x64asm are of the form write_att(), meaning use AT&T syntax. I
figured that since the regset was a home grown thing, it wasn't right to
print it and call it AT&T since it's really just AT&T like. Putting a
printer there also means that we'd have to define printers for things like
eflags, which don't have an AT&T syntax at all.

So I vote stoke, but I suppose I don't feel all that strongly about it.

On Wed, Oct 22, 2014 at 3:38 AM, Berkeley Churchill <
[email protected]> wrote:

https://imgflip.com/i/dcbcw

—
Reply to this email directly or view it on GitHub
#53 (comment).

from x64asm.

This issue is subsumed by issue #64. I'll take this over as part of that fix. Closing this now.

from x64asm.