[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: reading NaNs

This page is part of the web mail archives of SRFI 77 from before July 7th, 2015. The new archives for SRFI 77 contain all messages, not just those from before July 7th, 2015.

bear wrote:
So if we're going to have a NaN read/write syntax, we *MUST* require
implementors to guarantee that, no matter what, their reader will
never throw an error and return a NaN.

Okay, I'm comfortable with that.

Perhaps we need to defined a general invalid object which has (a) no read syntax and (b) is returned by read whenever it has a problem with the input (numbers too big, objects to big, bad syntax, etc.)


Dr Alan Watson
Centro de Radioastronomía y Astrofísica
Universidad Astronómico Nacional de México