| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
I don't see the use case to treat comments differently in the source file and in included files. do you know the reason?
Sorry, something went wrong.
|
The removeComments was added in #340 and it seems that it was added for performance reasons only, there is no known use case as far as I see when we want to only remove the comments in the included files. So I suggest that we just keep the removeComments flag. If that is false then keep all comments. If that is true the remove all comments. The performance optimisation might be less interesting after Tommys recent fix also so that files are not redundantly loaded. |
Sorry, something went wrong.
|
|
||
| { | ||
| const char code[] = "#define MACRO /* comment */\nMACRO\n"; | ||
| ASSERT_EQUALS("\n/* comment */", preprocess(code,dui)); |
There was a problem hiding this comment.
this may be questionable. do we want that comments are expanded. maybe the comment should only be kept on line 1.
but for now .. as far as I see it does not matter much. If somebody has strong opinions later and wants to change I am not against changing..
Sorry, something went wrong.
There was a problem hiding this comment.
gcc does copy comments in expansions. it will however turn c++-style comments in to c-style comments: https://gcc.gnu.org/onlinedocs/gcc/Preprocessor-Options.html
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
No description provided.