<html>
<body>
<font size=3>At 9/16/2010 01:38 PM, Paul C. Anagnostopoulos wrote:<br>
<blockquote type=cite class=cite cite="">At 9/16/2010 01:15 PM, Andrew
Whitworth wrote:<br>
<blockquote type=cite class=cite cite="">I personally don't like the idea
of ever leaving anything undefined.<br>
The C language is at a disadvantage because it was created so many<br>
years ago and because it's designed to run on so many different<br>
platforms.<br><br>
Parrot doesn't really have either of those problems. Parrot is a<br>
single standard platform, and we really don't need to be leaving<br>
values undefined anywhere. We really have three possible
behaviors:<br><br>
1) leave things undefined, which I think is bad<br>
2) Force some kind of integer conversion (INF -> INT_MAX, NAN -> 0,
etc)<br>
3) Throw an exception.<br><br>
I lean towards the third option. If somebody attempts an operation<br>
that is so clearly not a normal operation, we should proactively<br>
notify them about it, not silently do something strange and<br>
non-intuitive.</blockquote><br>
I agree that if we don't go with (1), we should go with
(3).</blockquote><br>
Then again, do we want Parrot_set_i_n and friends to check every single
number for Inf or NaN?<br><br>
~~ Paul<br>
</font></body>
</html>