2006/12/4, Kevin Ryde [EMAIL PROTECTED]:
While nosing around nearby stuff I noticed
(* 0 1.0) = 0
(* 0 1+1i) = 0
but
(* 1.0 0) = 0.0
(* 1+1i 0) = 0.0
which seems a bit inconsistent.
Indeed.
R5RS Exactness reads like either
exact or inexact is permitted,
-#ifdef HAVE_STRUCT_TIMESPEC
+#if HAVE_STRUCT_TIMESPEC || SCM_I_GSC_USE_PTHREAD_THREADS
pf (typedef struct timespec scm_t_timespec;\n);
Does the detection of struct timespec go wrong somehow?
The only timespec declaration on Win32 is the one in pthread.h, that's
why I or'ed
Mikael Djurfeldt [EMAIL PROTECTED] writes:
Good idea.
I made the change.
Because of paragraph 6.2.2, a program cannot expect to get
the result 0.0, and it seems like a strength of the implementation to
provide the additional piece of information that the result is indeed
*exactly* 0.
If
