"Jump to" not working for code appearing inside #ifdef's

[mark1977]

Hi,

I have parts of my code that are between #ifdef.....some code....#endif, and I compile with -fpp.

When I right click and choose "Jump to" for any routine that appears inside these statements, codeblocks is unable to find them.

My version is info is below.

Thanks!

------------------------------------------------------------------------------------------------

Name             : Code::Blocks
Version          : svn-r12045
SDK Version      : 2.2.0
Scintilla Version: 3.7.5
Author           : The Code::Blocks Team
E-mail           : in...@codeblocks.org
Website          : http://www.codeblocks.org

wxWidgets Library (wxMSW port)
Version 3.1.4 (Unicode: wchar_t, debug level: 1),
compiled at Apr  3 2020 09:35:29

Runtime version of toolkit used is 10.0.

[Darius Markauskas]

 Hello Mark

In my tested case, 'Jump to' works.

Perhaps you could disable "Interpret preprocessor directives" (see screenshot below) and see if "Jump to" now works. To be sure, close and reopen your project after changing these settings.

Could you, please, prepare a short test case which causes this problem?

--
You received this message because you are subscribed to the Google Groups "CBFortran" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cbfortran+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cbfortran/41e7ab5b-ac95-4312-b9cc-d74cf7185e90n%40googlegroups.com.

[mark1977]

Hi Darius,

Thanks for your reply. I do not have the "Interpret preprocessor directives" option available inside Configure Editor->Fortran Project, maybe my version is too old?

If not, I'll make a short test case as you suggest.

[Darius Markauskas]

 I thought you have latest C::B from cbfortran.sourceforge.io. If you have a bit older version, then it could be the opposite situation: C::B doesn't interpret preprocessor directives and therefore your code is parsed wrongly. Check on FSymbols browser if you find there names of procedures where you want to 'Jump to'.

The latest version of C::B tries to interpret pre-processor directives. However C::B does not always succeed. Preprocessor directives are tricky...

To view this discussion on the web visit https://groups.google.com/d/msgid/cbfortran/7af8911b-48c1-45d8-884d-93f7ace16e84n%40googlegroups.com.

[mark1977]

Under FSymbols browser, I don't see any names of procedures.

So, I updated to the latest version (1.8) and tried again. Same issue, regardless of whether "interpret preprocessor directives" is checked or not.

Here is the simplest code that reproduces the bug (compile with -fpp and -Dsomething):

!-------------------------------------------------------------------------

program exmaple1

call test

end

#ifdef something

subroutine test
print*,'success'
end

#endif

!------------------------------------------------------------------------------

[Darius Markauskas]

I just hope you are patient enough ;)

In your test case, C::B with "interpret preprocessor directives" disabled will function correctly. However, with "interpret preprocessor directives" enabled not, because C::B doesn't know anything about the "something" constant you defined on your command line. You should see the subroutine "test" shadowed on the editor. You can tell C::B (Fortran project plugin) about the defined constant on the Project->Properties dialog (see a screenshot).

To view this discussion on the web visit https://groups.google.com/d/msgid/cbfortran/77f6ac8c-4367-4793-a0d9-ab210f3b8eadn%40googlegroups.com.

[mark1977]

Hi Darius,

Thanks again for your reply. I confirm that in my test case, if I have "interpret preprocessor directives" disabled, it still does not function correctly. i.e. it still does not find the function when right clicking and choosing "Jump to". I attached 2 screenshots below. My current version is svn-r12309.

[Darius Markauskas]

Thank you Mark. Now I see the problem in C::B. It is some bug in the FP plugin. I hope I can find and fix it soon.

Darius

To view this discussion on the web visit https://groups.google.com/d/msgid/cbfortran/2555d240-04bf-4e98-bcb7-4f2ddbe05c6cn%40googlegroups.com.

[Darius Markauskas]

One more question: does C::B work as you expect when "interpret preprocessor directives" is enabled?

[mark1977]

No CB doesn't work as expected either way - i.e. it doesn't find the routine even when "interpret preprocessor directives" is enabled.

[Darius Markauskas]

"""No CB doesn't work as expected either way - i.e. it doesn't find the routine even when "interpret preprocessor directives" is enabled."""

Sorry, but I can't repeat it. On my system, C::B finds and jumps to "test" subroutine if "interpret preprocessor directives" is enabled AND

"something" is defined in the project properties dialog.

Perhaps you forgot to add "something" in Project->Properties dialog? (I am adding the screenshot again).

To view this discussion on the web visit https://groups.google.com/d/msgid/cbfortran/35999edc-c605-45b3-889a-4e7c641d6714n%40googlegroups.com.

[mark1977]

Sorry you are right I did forget to add "something" to the project properties. Now it works as expected.

[Darius Markauskas]

About the reported problem when the "Interpret preprocessor directives" option is disabled:

I have just committed required changes (very small) to the code of FortranProject plugin Rev.333.

Thank you Mark for reporting this issue.

To view this discussion on the web visit https://groups.google.com/d/msgid/cbfortran/df6cb31d-153c-4079-ac4b-84f3f09f241dn%40googlegroups.com.

[mark1977]

Thank you Darius, I'll try the new Rev.