Thanks for the reply, I wound up doing exactly that (geez, I think the code is identical to the letter!).
As per my original post, Johan, I offer this as a suggestion to add to the next release. I suspect comparing one POINT to another is a pretty common function, makes sense to be included I think.
...and so I said to Mr. Gates: "$640 billion should be enough for anyone!"
I'm not sure it's a good idea to unconditionally overload op== for POINTs in a library. Maybe make it a conditional option via a macro flag? Even if it's on by default, it lets us disable it if we need to.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum