Replies: 6 comments
-
I'm not familiar with this part of Poco, but have you checked that |
Beta Was this translation helpful? Give feedback.
-
@andrewauclair Thanks for your comment. Yes, file exists and file path is correct, during the debug session I can observe. The part that I could not understand, why I need to give two different objects for |
Beta Was this translation helpful? Give feedback.
-
The parameter is a |
Beta Was this translation helpful? Give feedback.
-
Yes you are right, but as I said does not make sense to me to just send |
Beta Was this translation helpful? Give feedback.
-
this is not released code, hence not a bug. I'l move it to discussions, and if you want to send a fix, you're welcome to do it |
Beta Was this translation helpful? Give feedback.
-
After digging into a little bit, I understood that how it works. So, the second parameter was for a file name which needs to be given to However, third parameter In this case, you need to generate precompiled version of the file with compiler "-E" option then you need to give it, now it works. However, naming convention, unit tests and description of this component has to be reviewed again, because without digging into, people could not understand the workflow. |
Beta Was this translation helpful? Give feedback.
-
Describe the bug
I have a simple header file (named "example.h") which needs to be parsed in order to get function name and type like below:
To Reproduce
To reproduce this problem only I need to write down such an example:
Expected behavior
I would expect that symbol size must be greater than zero but it always zero. At least I would expect to see that function name and type after call
printFunctionInfo
function.Logs
Screenshots
Please add relevant environment information:
-- [cmake] Build for OS type: Linux
-- [cmake] Build for OS version: 6.1.21.2-microsoft-standard-WSL2+
-- [cmake] Build for CPU type: x86_64
-- [cmake] Build type: release
-- [cmake] Build with cxx flags: -O3 -DNDEBUG
-- [cmake] Build with c flags: -O3 -DNDEBUG
-- Poco package version: 1.13.0
Additional context
Add any other context about the problem here.
Beta Was this translation helpful? Give feedback.
All reactions