Le 08/02/2017 à 10:25, FX a écrit :
Hi Steve,
I see Mikael has okayed the patch, but I did not have any time to comment
prior. I wanted to note that:
- the choice was deliberate, as the standard allows us to choose which real
kind REAL128 corresponds to when there are several matching choices. The idea
behind the current choice was to avoid forcing the use of slower soft-float
arithmetic when a hardware type existed. I don’t have a strong opinion myself
on the issue.
Hello, I didn’t have this in mind when I OKed the patch.
Still, I think the rule above goes against the principle of least surprise.
Actually I don’t really see the use case for these constants.
When would a user say; give me a real that big, including padding bits?
- Is this appropriate for stage 4?
Now that you remind of it, if we take the rules to the letter, no.
My opinion is that it should be accepted, in stage 4 or later.
But I don’t have a strong opinion about it either.
Mikael
