On 2/23/20 10:47 AM, Thomas Koenig wrote:
Hi Martin,
I was able to write a sanity check for these kind of issues, but it does
not resolve all similar issues for other keywords. It's not easy to do it.
Having looked at the origina awk code, I agree. Maybe, in the long
term, a lex/yacc grammar
Hi Martin,
I was able to write a sanity check for these kind of issues, but it does
not resolve all similar issues for other keywords. It's not easy to do it.
Having looked at the origina awk code, I agree. Maybe, in the long
term, a lex/yacc grammar with a monolithic C program to write out
t
On 2/20/20 7:08 PM, Thomas Koenig wrote:
Hi Martin,
Sure, I can improve sanity checking.
Thanks!
What exactly have you screwed up?
I had, in lang.opt
EnumValue
Enum (gfc_fcoarray) String (native) Value (GFC_FCOARRAY_NATIVE)
It was a bit non-obvious to me that this led to the whole sub-op
Hi Martin,
Sure, I can improve sanity checking.
Thanks!
What exactly have you screwed up?
I had, in lang.opt
EnumValue
Enum (gfc_fcoarray) String (native) Value (GFC_FCOARRAY_NATIVE)
It was a bit non-obvious to me that this led to the whole sub-option
being ignored due to
*drum roll*
th
On 2/20/20 8:29 AM, Thomas Koenig wrote:
Hi,
having just lost a few hours on a space in lang.opt where
there was supposed to be none, leading to a new option
being silently ignored, a request:
Hello.
Sure, I can improve sanity checking. What exactly have you screwed up?
Would it be possibl
Hi,
having just lost a few hours on a space in lang.opt where
there was supposed to be none, leading to a new option
being silently ignored, a request:
Would it be possible to improve the syntax checking for lang.opt?
It's a file that people touch only rarely, so it is likely that
they will have
