White-Tiger

I'd still say it's broken. If the user didn't break any rule, and the compiler becomes confused about which printf() to use, it's a broken compiler. In my case, I've noticed that MinGW forces one to include C++ headers before C headers.. So the following breaks because it's using the wrong "lli" PRIi64 define instead of the correct "I64i"; otherwise a working 189.5 KiB executable. #define __STDC_FORMAT_MACROS #include <time.h> #include <stdio.h> #include <inttypes.h> #include <string> int main(int...

I'd still say it's broken. If the user didn't break any rule, and the compiler becomes confused about which printf() to use, it's a broken compiler. In my case, I've noticed that MinGW forces one to include C++ headers before C headers.. So the following breaks because it's using the wrong "lli" PRIi64 define instead of the correct "I64i"; otherwise a working 189.5 KiB executable. #define __STDC_FORMAT_MACROS #include <time.h> #include <stdio.h> #include <inttypes.h> #include <string> int main(int...

your link doesn't explain the way \sa works.. that's why I've linked the explanation to how it actually behaves. If you read the \sa description, you'd get the impression that every word in there is a function / variable, yet every word is checked as one but doesn't need to be one. And yes... Doxygen usually checks for functions and variables in any comment (type) but has only specific formats it actually parses like <func>(params) and ::variable (and others) while a \sa matches every single word...

well... a Doxygen example would look like: \sa Inside a see also section any word is checked, so EType, Val1, GVal1, ~Autolink_Test and member will be replaced by links in HTML. as seen here: https://www.stack.nl/~dimitri/doxygen/manual/autolink.html So that basically means that a real Doxygen is smart enough to detect "valid" links and only creates those.. Is it possible for our Code::Blocks plugin to verify names as required? I've seen other places that lack such "verification"...

This is how it looks on Windows. (default size) And I can confirm that resizing works...

now, if one could implement the suggested drop-down menu items to enhance/improve...

oh right... my patch to src/plugins/codecompletion/parser/parser_base.cpp only covered...

I've wrote a basic implementation, but it only does substring tests, so it's not...