Closed zaikunzhang closed 2 years ago
You are indeed onto something, it would appear that the regex handling use
statements only contains INTRINSIC
.
see: https://github.com/hansec/fortran-language-server/blob/e8479e89cf36c7fea5fed94cf5cb2de6c867ff51/fortls/parse_fortran.py#L17
I suspect that this might be a bigger pain than simply doing INTRINSIC|NON_INTRINSIC
and read_use_stmt
might need a small edit as well.
I suspect that this might be a bigger pain than simply doing
INTRINSIC|NON_INTRINSIC
andread_use_stmt
might need a small edit as well.
Thank you, @gnikit , for the response!
I edited only USE_REGEX
as you mentioned, but the problem persists. What edition would be needed for read_use_stmt
? Sorry that I do not code Python, so I could not figure it out myself.
Thanks and regards, Zaikun
The fix for this should be (INTRINSIC|NON_INTRINSIC)
that is all. I will be pushing a patch in my fork
@zaikunzhang FYI this has been in fortls
since v1.14.3 (currently fortls is in v2.0.1)
Hello @gnikit ! Thank you very much for fixing this issue! Sorry that I missed your previous comment in December. I will try the new version.
First of all, thank you for this great work!
With
fortls 1.12.0
, I get a false positive about "Object not found in scope". Here is a minimal working example.fortls
complains thatObject "dp" not found in scope
in the programtestls
. The complaint will disappear if we replacewith
Thank you for your attention.