[Bug libfortran/89696] A potential bug with read() when parsing number from string

2019-03-13 Thread kevin at fai dot host
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89696 --- Comment #11 from Khang H. Nguyen --- That is cool with me if you think it that way. But I don't think you would be very happy parsing " 123 4" and still get the same result as "1234". Or if you were to give it a blank string and get 0 where

[Bug libfortran/89696] A potential bug with read() when parsing number from string

2019-03-13 Thread sgk at troutmask dot apl.washington.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89696 --- Comment #10 from Steve Kargl --- On Wed, Mar 13, 2019 at 07:36:10PM +, kevin at fai dot host wrote: > > --- Comment #9 from Khang H. Nguyen --- > No, no, you got me wrong, it is not a tutorial. You got it wrong. > I just see so much ins

[Bug libfortran/89696] A potential bug with read() when parsing number from string

2019-03-13 Thread kevin at fai dot host
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89696 --- Comment #9 from Khang H. Nguyen --- No, no, you got me wrong, it is not a tutorial. You got it wrong. I just see so much insecure with the statement read, of which I think it more like a procedure. That is why I am trying to report the bug.

[Bug libfortran/89696] A potential bug with read() when parsing number from string

2019-03-13 Thread sgk at troutmask dot apl.washington.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89696 --- Comment #8 from Steve Kargl --- On Wed, Mar 13, 2019 at 07:17:42PM +, kevin at fai dot host wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89696 > > --- Comment #6 from Khang H. Nguyen --- > Sorry, if I am wasting your time. bug

[Bug libfortran/89696] A potential bug with read() when parsing number from string

2019-03-13 Thread sgk at troutmask dot apl.washington.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89696 --- Comment #7 from Steve Kargl --- On Wed, Mar 13, 2019 at 07:09:19PM +, kevin at fai dot host wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89696 > > --- Comment #5 from Khang H. Nguyen --- > > program foo > > integer i > > re

[Bug libfortran/89696] A potential bug with read() when parsing number from string

2019-03-13 Thread kevin at fai dot host
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89696 --- Comment #6 from Khang H. Nguyen --- Sorry, if I am wasting your time. I just have an addition to add to the above. If you use formatting. For example, in a case like this below, it will not give a correct value, as now leading spaces will b

[Bug libfortran/89696] A potential bug with read() when parsing number from string

2019-03-13 Thread kevin at fai dot host
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89696 --- Comment #5 from Khang H. Nguyen --- > program foo > integer i > read(*,*) i > read(*,'(I4)') i > end program foo > > % gfcx -o z a.f90 > % ./z > % ./z > 12 b > 12 b > At line 4 of file a.f90 (unit = 5, file = 'stdin') > Fortran runtime

[Bug libfortran/89696] A potential bug with read() when parsing number from string

2019-03-13 Thread kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89696 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org --- C

[Bug libfortran/89696] A potential bug with read() when parsing number from string

2019-03-13 Thread kevin at fai dot host
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89696 --- Comment #3 from Khang H. Nguyen --- Sorry, I just have one more quick question. Bug 1: Nonetheless, for read(), I was just wondering, if you read from a list input then it should be like that. However, if it is just a raw string and it act

[Bug libfortran/89696] A potential bug with read() when parsing number from string

2019-03-13 Thread kevin at fai dot host
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89696 --- Comment #2 from Khang H. Nguyen --- okay, thank you for the information, I did not know that.

[Bug libfortran/89696] A potential bug with read() when parsing number from string

2019-03-13 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89696 Thomas Koenig changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|