cpp.hint
-
if you utilize Visual Studio and C++ you know IntelliSense likes a so called hint file i.e. "cpp.hint" . as far as i know no automatic means to generate this file exists . as i find manually entering each macro tedious and usually forget to do so at time of writing each macro and as i found current project has more than 1000 macros i wrote a C program to generate said hint file . i don't know how others solve this problem however if any would find this code useful i can provide same after polishing up the last 2% .
-
if you utilize Visual Studio and C++ you know IntelliSense likes a so called hint file i.e. "cpp.hint" . as far as i know no automatic means to generate this file exists . as i find manually entering each macro tedious and usually forget to do so at time of writing each macro and as i found current project has more than 1000 macros i wrote a C program to generate said hint file . i don't know how others solve this problem however if any would find this code useful i can provide same after polishing up the last 2% .
I haven't used VS in years, but if it's a common problem people face these days then it's a great candidate for an article. Perhaps it could be your first one.
Jeremy Falcon
-
if you utilize Visual Studio and C++ you know IntelliSense likes a so called hint file i.e. "cpp.hint" . as far as i know no automatic means to generate this file exists . as i find manually entering each macro tedious and usually forget to do so at time of writing each macro and as i found current project has more than 1000 macros i wrote a C program to generate said hint file . i don't know how others solve this problem however if any would find this code useful i can provide same after polishing up the last 2% .
first time I've heard about that. will go educate myself.
CI/CD = Continuous Impediment/Continuous Despair
-
if you utilize Visual Studio and C++ you know IntelliSense likes a so called hint file i.e. "cpp.hint" . as far as i know no automatic means to generate this file exists . as i find manually entering each macro tedious and usually forget to do so at time of writing each macro and as i found current project has more than 1000 macros i wrote a C program to generate said hint file . i don't know how others solve this problem however if any would find this code useful i can provide same after polishing up the last 2% .
If anyone else is wondering like I was: Hint Files | Microsoft Learn[^] I'm always torn when it comes to
#definemacros. I've had a number of cases where that was the cleanest way to solve a problem, but I've always felt vaguely guilty about it. My intuition says that if you need to supply a "hint file", maybe you're overdoing it in the macro department.Software Zen:
delete this; -
if you utilize Visual Studio and C++ you know IntelliSense likes a so called hint file i.e. "cpp.hint" . as far as i know no automatic means to generate this file exists . as i find manually entering each macro tedious and usually forget to do so at time of writing each macro and as i found current project has more than 1000 macros i wrote a C program to generate said hint file . i don't know how others solve this problem however if any would find this code useful i can provide same after polishing up the last 2% .
We have a program that needs a fair few code macros to generate boiler-plate. We simply define those macros only in cpp.hint and include that file to bring in the macros where needed. Of course we're only doing this to keep Visual Studio "intellisense" happy.
-
We have a program that needs a fair few code macros to generate boiler-plate. We simply define those macros only in cpp.hint and include that file to bring in the macros where needed. Of course we're only doing this to keep Visual Studio "intellisense" happy.
thanks that seems a good idea . i will have to be careful re/ naming so as to not duplicate . thank you again