... interpreted as zero, input like +E and -E- should be legal by the standard. Blanks aren't interpreted as zero in list directed input. They're value separators (unless they are in a character input string). Also, 10.7.6 on the BN abd BZ edit descriptors says "The blank interpretation mode affects only numeric editing (10.6.1) and generalized numeric editing (10.6.4.1) on input." ...

... Yes, *BUT*... It is critically important to distinguish whose error it is. t isn't just an... would do something like quietly replace any problematic character with a blank. I was dissapointed to find that... OP is doing here. I'd try to distinguish different possible input types based on whether I ... reliably, you need to read the data as character data and then do your own checks. Depending...

... way). A second question: how do I enter a '/' character? Well, you have a .co.uk address, so the '/' key ... works as required but the Intel version now interprets '+' as a number (as well as '.', ',' and '-'): is that an Intel bug? ... the customer can report zero glitches rather than having to fix some number of their own past clevernesses.

...: how do I enter a '/' character? Well, you have a .co.uk... version now interprets '+' as a number (as well as '.', ',' and '-'): is ...(8) :: x integer :: n, ios character(10) :: buff do write(6,'(... write(6,'(a,f10.0)') 'Number:',x cycle 900 continue write(...write(6,'(a,f10.0)') 'Number:',x cycle 900 continue write(...

... second question: how do I enter a '/' character? Well, you have a .co.uk address, ...but the Intel version now interprets '+' as a number (as well as '.', ',' and '-'): is that an Intel... real(8) :: x integer :: n, ios character(10) :: buff do write(6,'(a)',advance='... x write(6,'(a,f10.0)') 'Number:',x cycle 900 continue write(6,'(2a)')...

...other compilers behave the other way). A second question: how do I enter a '/' character? Well, you have a .co.uk address, so the '/' key should be on the left of ... behaviour - the g95 version works as required but the Intel version now interprets '+' as a number (as well as '.', ',' and '-'): is that an Intel bug? Extensions! Treating "+","-" and ...

... second question: how do I enter a '/' character? Well, you have a .co.uk address, ...but the Intel version now interprets '+' as a number (as well as '.', ',' and '-'): is that an ... real(8) :: x integer :: n, ios character(10) :: buff do write(6,'(a)',advance='... x write(6,'(a,f10.0)') 'Number:',x cycle 900 continue write(6,'(2a)')...

...: how do I enter a '/' character? Well, you have a .co.... version now interprets '+' as a number (as well as '.', ',' and '-'): is ...0. Command:. , Number: 0. Number: 0. program ex implicit none real(8) :: x integer :: n, ios character(10) :: buff do write(6,'(a...write(6,'(a,f10.0)') 'Number:',x cycle 900 continue write(...

... result but perhaps the standard is ambiguous on this. Is this a g95 bug? I'd have the same expectation that you have, so I guess there's A second question: how do I enter a '/' character? Well, you have a .co.uk address, so the '/' key should be on the left of your right shift key ;-) Hum, more seriously, you need to change your read's into: read(5,'(a)') buff ...

... same expectation that you have, so I guess there's a bugreport to make (or at least feature request, as lots of other compilers behave the other way). A second question: how do I enter a '/' character? Well, you have a .co.uk address, so the '/' key should be on the left of your right shift key ;-) Hum, more seriously, you need to change your read's into: read(5,'(a)') buff...