Re: CA broken; how do I differentiate NSValues for size and point?

[Ivan Vučica]

Thanks for all the attention you've given to this!

On Sun, May 27, 2018 at 10:29 PM Fred Kiefer <address@hidden> wrote:

> Sorry, you seem to be using an unusual mail format that my Apple Mail
isn’t able to properly reply to.

I hit reply-to-all in Gmail, then I hit enter where I want to inline reply.
I don't have insight into what Gmail does before sending.

I'll switch to plaintext only (which I wanted to use anyway), which should
help.

> > I am in favor of leaving the bug open on Savannah and Github, then? I
can no longer reproduce the original issue after updating to the latest
fixes, but if you believe the solution that's in place is hacky, maybe the
bugs can be repurposed.
> >
> > Otherwise, I am fine with them being closed (as the immediate
NSSize/NSPoint problem no longer persists).

> No, keep the two bug reports open. It might be that when we come up with
a fix we will forget to close one of them. Please keep an eye open for that
case and remind me.

Ah -- it's unlikely I'll remember something you won't :-)

Maybe you can assign the bug(s) to yourself, so they appear in bug
dashboards?


> > PS: In your test code the second PASS is missing a „!“.
> >
> > It doesn't; @encode(NSPoint) should be different than @encode(NSSize).
> >
> > I actually added comments to the new test case I pushed to my personal
repo, so it should be clearer what's going on.

> I was referring to this line:

>   PASS(result, "@encoding(NSSize) == pointV objCType“);

> And there you check that the two values are not equal, which in C like
programming languages is done via a negation that is missing in the
description string.

Oh, right. Sorry. That was an oversight which I corrected after sending the
email. :-)

> I really should be more verbose in my writing. The reason here is that I
am no longer used to communications in English. Sorry for that.

I hope to be in that situation again someday ;-)