fmt: Scanf rejects \r\n at end of line on Windows

[gopherbot]

by xuxinhua1984:

The code:

package main

import (
    "fmt"
)

func main() {
    for i := 0; i < 2; i++ {
        var name string
        fmt.Print("Input Name:")
        n, err := fmt.Scanf("%s", &name)
        fmt.Println(n, err, name)
    }   
}

Build And Run.

Then, I input:golang，and enter，the result is:

Input Name:golang
1 <nil> golang
Input Name:0 unexpected newline

But on linux，the same code, the result is ok:

Input Name:golang
1 <nil> golang
Input Name:golang
1 <nil> golang

The reason is: on windows, The "enter" is "\r\n", but in fmt
package, it is only deal "\n".

[gopherbot]

Comment 1 by xuxinhua1984:

When I use fmt.Scanln(&name) or fmt.Scanf("%s\n", &name), it is OK!

[davecheney]

Comment 2:

Hello, is there anything actionable in this issue, or may it be closed ?

Status changed to WaitingForReply.

[gopherbot]

Comment 3 by opnieuw1280:

Hello one should either acknowledge that semantics are OS-dependendent or change
implementation (ASAP!) - I think damage is already done so leaves first option.
The root problem of course is that some OS-s do not have an opaque record structure
for files. (this includes Unix as well as Windows - still rather silly - once details
are visible they are bound to be different )

[rsc]

Comment 5:

Labels changed: added priority-later, go1.2maybe, removed priority-triage.

Status changed to Thinking.

[robpike]

Comment 6:

This issue was closed by revision 221af5c.

Status changed to Fixed.