[Scheme-reports] Small comments on draft 3

[Sven Hartrumpf <hartrumpf@x>]

Hi all.

First, let me say:

Thanks for this excellent work - I hope WG 2 will be as good as WG 1!


Second, here are my comments ("only" from a heavy-user perspective)
in reading order:

p. 1
Author block
Is the non-alphabetical order of the 8 authors intended?
Oh, you sorted on first name? That is unusual.
"Pym" should be capitalized, I guess.

p. 1
"standardized implementation features" ->
"standardized implementation feature identifiers"

p. 6
"byte" should be listed in 1.3.3.

p. 6
"By convention, the value returned by a mutation procedure is unspecified."
Why not returning the modified object?
This makes many program changes much easier.

p. 24
"include-ci" seems to be very technical. Is #!fold-case not enough?

p. 24
"(define (make) (list ()))"
...
"(set-car! s ())"
No quotes?

p. 41
"fill" arguments (and on other pages, global):
Should be better named "obj".

p. 41
"vector-fill!"
Why no optional "start" and "end"?

p. 42
"partial-bytevector-copy!" ->
"bytevector-copy-partial!"

p. 42
"string-map ... when the shortest list" ->
"string-map ... when the shortest string"

p. 43
"vector-map ... when the shortest list" ->
"vector-map ... when the shortest vector"

p. 48
"string. raise":
Please capitalize identifiers at sentence start, for consistency.
There might be more cases like this.

p. 50
"(close-port port) ...":
formatting broken

"the first two" ->
"the last two"

Why are the popular abstractions
"call-with-input-string" and "call-with-output-string" omitted?

p. 51
"before any linefeed character":
What about a carriage return described below?

p. 51
"and display is for" ->
"and display for"
Parallel construction.

p. 52
Why does "delete-file" not return the success of the operation?

p. 64 - 64:
All lists of procedures should be sorted for ease of reference.

p. 64
"scheme char normalization"
This looks like a "submodule" of "scheme char", does not it?
If so, how about "scheme char-normalization"?

p. 64
"These features are used by cond-expand to conditionally include
module declarations in a module." ->
"These feature identifiers are used by cond-expand."
(Delete the "to ..." part because it is only half of a story
that has already been told by the report.)

p. 65
"C memory model flags"
Add a ".".

p. 65
"<name-version>"
Can this be easily extended to version intervals?
I am tired of writing
"(cond-expand ((or bigloo2.9a bigloo2.9b <and 20 more>) ..."
and extending such lists in many places several times a year.
(Same for other implementations, of course.)

p. 68
All BibTeX references should have a year attribute.
These have none: 1, 2, 4, 9, 17, 23

"To appear" for a publication from 1998 is a little outdated.

"et al." should be avoided in author lists.


Ciao
Sven

_______________________________________________
Scheme-reports mailing list
Scheme-reports@x
http://lists.scheme-reports.org/cgi-bin/mailman/listinfo/scheme-reports