[R6RS] issue straw poll

dyb at cs.indiana.edu dyb at cs.indiana.edu
Thu Oct 19 19:41:35 EDT 2006


Here is a straw poll covering the "non-routine" entries currently active
in the tracking system.  Please indicate your inclination on each question
by entering one of Y, M, or N after each "yes/maybe/no (Y/M/N):  " prompt. 
If you leave an entry blank, I'll treat it as M, but I'd prefer you
expliclty write M so I can be sure you didn't simply forget to vote on
that issue.  My thinking is that we'll discuss *all* of these issues at
some point no matter how the straw poll comes out, so this truly is a
non-binding poll just to get a sense of where we stand.

Please send me your responses by Thursday, October 26.  I will send out a
summary once I receive all responses.

For issues upon which we vote either unamimously Y or unamimously N, I
will post an informal response to r6rs-discuss giving the sense of the
committee.

Kent

--------

6  Applicable record instances
   Should we add them?
   yes/maybe/no (Y/M/N): 

7  Additional LAZY primitive for delayed evaluation
   Should we add it?
   yes/maybe/no (Y/M/N): 

9  backslash-linefeed
   Should we allow <intraline whitespace> between the \ and <linefeed>
     in \<linefeed><intraline whitespace>?
   yes/maybe/no (Y/M/N): 

10 #;<datum> comments useless
   Should we flush?
   yes/maybe/no (Y/M/N): 

11 NaN is not a real number
   Should we make (real? <any NaN>) #f?
   yes/maybe/no (Y/M/N): 

12 R6RS library syntax should include a standard format for importing SRFI libraries
   Should we do this?
   yes/maybe/no (Y/M/N): 

14 <hex scalar value> should allow only 6 digits
   Should we limit to 6 digits?
   yes/maybe/no (Y/M/N): 
   Should we eliminate restriction on number of digits?
   yes/maybe/no (Y/M/N): 

17 "An exception might be raised" considered confusing
   Change to "An exception should not be raised"?
   yes/maybe/no (Y/M/N): 

18 String exit codes should be allowed
   Should we allow them?
   yes/maybe/no (Y/M/N): 

22 U+0085 is whitespace
   Should we make U+0085 whitespace?
   yes/maybe/no (Y/M/N): 

25 "forall" and "exists" should use SRFI-1 equivalents
   Should we rename?
   yes/maybe/no (Y/M/N): 

26 Map and for-each should work even if lists are of unequal length
   Should we make this change?
   yes/maybe/no (Y/M/N): 

27 Some generic arithmetic procedures should be put in a library
   Should we do this?
   yes/maybe/no (Y/M/N): 

36 Ambiguous call/cc-behaviour of list operations
   Should we make the benavior unambiguous?
   yes/maybe/no (Y/M/N): 

38 Position-significance of declarations in scripts
   Should we allow them only at the front of a script body?
   yes/maybe/no (Y/M/N): 

39 Script-body differences
   Should we make script bodies like library/lambda bodies?
   yes/maybe/no (Y/M/N): 
   Should we make library/lambda bodies like script bodies?
   yes/maybe/no (Y/M/N): 

40 Exactness is orthogonal to type
   Should we eliminate statement that exactness is orthogonal to type?
   yes/maybe/no (Y/M/N): 
   Should we eliminate sections 16.5 "exact arithmetic" and 16.6 "inexact arithmetic"
   yes/maybe/no (Y/M/N): 

42 Requirement to detect circular lists
   Should we eliminate this requirement?
   yes/maybe/no (Y/M/N): 

45 last-element behavior of for-each
   Specify return value of for-each to be the unspecified value?
   yes/maybe/no (Y/M/N): 

46 LF should not be the only line separator
   Specify larger set of line separators?
   yes/maybe/no (Y/M/N): 

47 Add (sort) and (vector-sort!) procedures
   Should we add them?
   yes/maybe/no (Y/M/N): 

49 Higher-order procedures should not interfere with exceptions
   Should we prohibit this "interference"?
   yes/maybe/no (Y/M/N): 

51 Conflating programs and scripts
   Add a separate notion of program?
   yes/maybe/no (Y/M/N): 
   Remove <script header> from scripts?
   yes/maybe/no (Y/M/N): 

52 Exact-Integer and Real (and Complex) are more useful distinctions than Exact and Inexact
   Adopt SRFI-94 and flush 16.5 "exact arithmetic" and 16.6 "inexact arithmetic"?
   yes/maybe/no (Y/M/N): 

58 only 'big' and 'little' as endiannness may not be enough
   Should we add others or allow extensions?
   yes/maybe/no (Y/M/N): 



More information about the R6RS mailing list