Re:Modern C++ for C Programmers: part 5
by mikec3010 on Wednesday July 25, 2018 @11:17AM
(#17609909)
Certain IDE vendors could solve this if they really cared about UX. Not by implementing modules, but by efficiently scanning vast directories for versions of headers, and arranging them in a visually navigable manner (you know, actually being a useful IDE). The last time I used one, the OS was incapable of even searching folders. Partial string matching of filenames was apparently too complex for it to handle.
[ Parent
| on HN ]
Re:Modern C++ for C Programmers: part 5
by hermitdev on Wednesday July 25, 2018 @05:02PM
(#17612777)
If you have your IDE properly configured with the include dirs needed to build, at least MSVC can autocomplete for you. Personally, I don't rely on this, as I do most of my C++ work from the command line using bash, vim & make.
Can't explain why, but for C++ projects, I intuitively remember what paths I need for headers, but for a C# project, I rely upon autocomplete as a crutch. Maybe it's just how much more time I spend doing C++ work and the time I spend with the libraries I use vs the relatively small time I spend with C#.
Re:Modern C++ for C Programmers: part 5
by mikec3010 on Wednesday July 25, 2018 @06:37PM
(#17613561)
> If you have your IDE properly configured
You're misunderstanding me. I'm saying the IDE should discover headers for me. MSVC refers me to a Byzantine series of clicks, drop downs, text input, and OK buttons. That interface hasn't changed for 20 years
A proper modern UX would scan for valid headers in a dir, then allow me to choose which ones to "import" into the workspace. Not make me hunt for them through an antiquated and inefficient UI