Re: [Scheme-reports] Formal Comment: add write-string to (scheme base)

[Andrew Robbins <andjrob@x>]

I would suggest keeping 'display' and adding a comment stating that:

"
If this procedure was named in accordance with other functions, it
would be named 'write-string', but for historical reasons it is named
'display' in order to maintain compatibility with previous revisions
of this report.
"

or something to that effect. Such a comment might be left for a
rationale document like R6RS has.

If I may rant, I've noticed many of these rename issues. Just to name
a few: cons*=list*, fold=fold-left, reduce=reduce-left,
get-char=read-char, get-u8=read-u8, lookahead-u8=peek-u8,
lookahead-char=peek-char, for-all=every, exists=any, etc.

Both R6RS and the current R7RS drafts have import and export renaming
systems (however, I feel obliged to remind/inform that R6RS and
R7RS-small export renaming are incompatible), this should provide
sufficient support to easily modify the language to suit anyone's
needs. For example, you could write a library which does all this
renaming for you, and it would probably end up being a one-liner.

Regards,
Andrew Robbins

On Wed, Jun 27, 2012 at 4:47 PM, Arthur Smyles <atsmyles@x> wrote:
> Looking closer I see alot of missing string functions where there is an
> analogous bytevector procedure
>
> examples: read-string, read-string!, write-partial-string
>
> Arthur
> On 6/27/12 4:34 PM, Arthur Smyles wrote:
>
> Formal Comment
>
> Submitter's Name: Arthur Smyles
> Submitter's Email Address: atsmyles at verizon.net
> Draft Version of Report: 6th
> Section of draft R7RS: 6.13.3. Output
>
> Summary:
>
> Add write-string procedure to (scheme base)
>
> Full Description:
>
> For binary-ports there are the procedures write-u8 and write-bytevector.
> However, for textual ports there is only write-char. This proposal requests
> the addition of write-string. It may be argued that display already provides
> this, however it is in a library that is optional. Strings written with
> write-string are not enclosed in double quotes, and no characters are
> escaped within those strings. Change display procedure for strings to say
> that they are written as if written by write-string.
>
>
>
>
> _______________________________________________
> Scheme-reports mailing list
> Scheme-reports@x
> http://lists.scheme-reports.org/cgi-bin/mailman/listinfo/scheme-reports
>
>
>
>
> _______________________________________________
> Scheme-reports mailing list
> Scheme-reports@x
> http://lists.scheme-reports.org/cgi-bin/mailman/listinfo/scheme-reports
>

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