I have compiled another project of SciGraph and upon running I get an array bounds exceeded at the piece of code in SciCenter below:
nsstart=1 ! trash leading blanks
DO WHILE (text(nsstart:nsstart) .EQ. ' ')
nsstart=nsstart+1
END DO
It occurs when there is no value of text and the while loop runs into the error.
Is there a compiler setting that allows better handling of this?
I don't remember running into this when I first used the original workspace that came with the software.
Thanks for any help!
Ken
nsstart=1 ! trash leading blanks
DO WHILE (text(nsstart:nsstart) .EQ. ' ')
nsstart=nsstart+1
END DO
It occurs when there is no value of text and the while loop runs into the error.
Is there a compiler setting that allows better handling of this?
I don't remember running into this when I first used the original workspace that came with the software.
Thanks for any help!
Ken
链接已复制
3 回复数
This is actually a bug in the Scigraph code that we found and fixed in 6.6. It has to do with the code that is trying to strip leading blanks from titles. The new code looks like this:
This occurs several places in SGLOWLVL.F90
Steve
nsstart=1 ! trash leading blanks DO WHILE (text(nsstart:nsstart) .EQ. ' ') nsstart=nsstart+1 if (nsstart > len(text)) exit END DO
This occurs several places in SGLOWLVL.F90
Steve
Steve, Are there any other declarations for using the added line of code?
I got a syntax error pointing to the "Len" saying found whitspace when expecting other.
Also could not find >l in language quide. What is that?
Thanks
Ken
I got a syntax error pointing to the "Len" saying found whitspace when expecting other.
Also could not find >l in language quide. What is that?
Thanks
Ken
Sorry - that was supposed to be the HTML code for a greater-than sign. I fixed it.
We made a lot of changes to SCIGRAPH - but I don't think other declarations were needed. I'd have to go back and compare the versions. If you upgrade to 6.6, you'll get the new code.
Steve
We made a lot of changes to SCIGRAPH - but I don't think other declarations were needed. I'd have to go back and compare the versions. If you upgrade to 6.6, you'll get the new code.
Steve
