Re: [go-nuts] Fscan() eats 1st char in scanning values

>> Fscanln is when you want to scan *the entire line* in one go, and you know in advance exactly the right number of placeholders to capture. Yes, Brain. This means the documentation needs to be changed a bit, like the blue text in my previous message. And of course, my example of the fix is no

Re: [go-nuts] Fscan() eats 1st char in scanning values

Hi Jan Thank you for the test enhancing. Please read my answer to Howard https://groups.google.com/g/golang-nuts/c/tzvKTyaugEk/m/5h2Sm03bDgAJ thanks ivan On Monday, January 27, 2025 at 9:37:46 PM UTC+3 Jan Mercl wrote: > On Mon, Jan 27, 2025 at 6:54 PM 'Ivan Burak' via golang-

Re: [go-nuts] Fscan() eats 1st char in scanning values

Hi Howard Thank you for the answer. My data is easier, it contains only 2 lines: Go version go1.22.11 windows/amd64 Build simple, secure, scalable systems with Go I did some tests and to speedup coding decided to use Fscanln(). I don't use this function in real programming, it's too slow. Ther

Re: [go-nuts] Fscan() eats 1st char in scanning values

erous just continue to read till the newline. So concerning the documentation after successful reading the first value in a line we should continue the scanning. [image: FscanlnErr.png] `ivan` On Monday, January 27, 2025 at 7:36:39 AM UTC+3 Ian Lance Taylor wrote: On Sun, Jan 26, 202

[go-nuts] Fscan() eats 1st char in scanning values

Fscan() eats 1st char in scanning values if the values aren't a first value in a line. The documentation tells: "Fscanln is similar to Fscan , but stops scanning at a newline and after the final item there must be a newline or EOF." The test discover