idaho Messages: 6 Registered: April 2007 Location: Frankfurt-am-Main
Promising Member
Hi, folks,
Perhaps, someone has already asked this question but I couldn't find a solution - if there is one. Is it possible to auto-complete symbols from OS-specific headers, like <windows.h>, e.g? Not a big issue, of course, but it would certainly come handy at times.
cbpporter Messages: 1401 Registered: September 2007
Ultimate Contributor
Actually there is a workaround. You can create a package based the library you want to use and with a little luck it will work fine. It can be a dummy package (i.e. only headers).
Actually there is a workaround. You can create a package based the library you want to use and with a little luck it will work fine. It can be a dummy package (i.e. only headers).
Thats true and it is also true that in one point in the past, I was experimenting with "automatic external header package".
Anyway, all of that failed, because system headers are usually extremely full of macros -> results of parsing were nil.
That is why I believe we must deal with macros first, then do external headers.
cbpporter Messages: 1401 Registered: September 2007
Ultimate Contributor
Couldn't we have in the first phase a weak preprocessor that only preprocesses external headers in order to determine the program structure and without these macros affecting .cpp files? I mean preprocess <stdio.h> and all it's includes, parse once that file to determine what functions it contains, cache and make that list available to .cpp files without actually having those macros effect the way Assiste++ sees out .cpp files? This implementation would be much easier.
Couldn't we have in the first phase a weak preprocessor that only preprocesses external headers in order to determine the program structure and without these macros affecting .cpp files? I mean preprocess <stdio.h> and all it's includes, parse once that file to determine what functions it contains, cache and make that list available to .cpp files without actually having those macros effect the way Assiste++ sees out .cpp files? This implementation would be much easier.
Members
Pages
Help
Register
Login
Home
