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

On Mon, Jan 27, 2025 at 6:54 PM 'Ivan Burak' via golang-nuts wrote: WAI: https://go.dev/play/p/4bWHGemItL_9 -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to gola

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

In your example, you are repeatedly reading one 'item' from the line. This is the source of the confusion, as this is not how Fscanln works - when you do this, *each* item is the documented 'final item' after which there must be a newline. That is, your data would look more like this: space sep

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

Hi Ian >> Check the error result from Fscanln. Thank you for the advice but I still have some arguments about wrong behavior of Fscanln() or not fully correct documentation for it.. Let’s look at the next lines from the documentation. *func **Fscan*