U++ framework: U++ TheIDE: CodeEditor, Assist++, Topic++ » Auto-completion for external headers

Home » U++ TheIDE » U++ TheIDE: CodeEditor, Assist++, Topic++ » Auto-completion for external headers

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

Auto-completion for external headers [message #21623]

Sat, 30 May 2009 02:52

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.

Thanks in advance.

Report message to a moderator

Re: Auto-completion for external headers [message #21710 is a reply to message #21623]

Mon, 01 June 2009 19:47

mirek
Messages: 14291
Registered: November 2005

Ultimate Member

idaho wrote on Fri, 29 May 2009 20:52

Hi, folks,

Perhaps, someone has already asked this question but I couldn't find a solution - if there is one.

Under development.

The problem is that external headers are usually macro-heavy and macros cause big problems if you want to be fast.

Anyway, it is coming. I hope it will be working at the end of year, hopefully much sooner.

Mirek

Report message to a moderator

Re: Auto-completion for external headers [message #21907 is a reply to message #21710]

Wed, 10 June 2009 11:10

cbpporter
Messages: 1428
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).

Report message to a moderator

Re: Auto-completion for external headers [message #21940 is a reply to message #21907]

Thu, 11 June 2009 19:34

mirek
Messages: 14291
Registered: November 2005

Ultimate Member

cbpporter wrote on Wed, 10 June 2009 05:10

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.

Mirek

Report message to a moderator

Re: Auto-completion for external headers [message #21950 is a reply to message #21940]

Thu, 11 June 2009 23:34

cbpporter
Messages: 1428
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.

Report message to a moderator

Re: Auto-completion for external headers [message #21952 is a reply to message #21950]

Thu, 11 June 2009 23:45

mirek
Messages: 14291
Registered: November 2005

Ultimate Member

cbpporter wrote on Thu, 11 June 2009 17:34

I think I will go "full solution"...

Mirek

Report message to a moderator

Previous Topic:	A few suggestions about CodeEditor
Next Topic:	Handling of namespaces in Navigator and code analyzer

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sun Jun 07 10:06:44 GMT+2 2026

Total time taken to generate the page: 0.00522 seconds