Developer forums (C::B DEVELOPMENT STRICTLY!) > CodeCompletion redesign

Code Completion fails at extern declared functions

<< < (2/3) > >>

MortenMacFly:

--- Quote from: christobal on December 01, 2009, 02:22:15 pm ---That is right, but if a library is used, the implementation is not part of the project.

--- End quote ---
It's pretty weird to declare a declaration for a library function as "extern" in the interface, isn't it?!
However, yes - it's reproducible.

christobal:

--- Quote ---It's pretty weird to declare a declaration for a library function as "extern" in the interface, isn't it?!
--- End quote ---

I have to admit that it has no effect on function declarations, but it is necessary for declarations of variables. Could you confirm that the patch above works correctly? I don't have a clue about the codecompletion plugin and so it's just a wild guess... :)

ivan1979:
Hi,

i'm very interesting  in a libcodecompletion.so that implements extern resolution also, can anyone help me?
where can i found it?
Actually i include in mu C::B C parser a gcc arm toolchain and very many functions are declarated as extern so codecompletion cannot resolve those  :(
Thanks

ollydbg:

--- Quote from: ivan1979 on March 12, 2010, 03:49:19 pm ---Hi,

i'm very interesting  in a libcodecompletion.so that implements extern resolution also, can anyone help me?
where can i found it?
Actually i include in mu C::B C parser a gcc arm toolchain and very many functions are declarated as extern so codecompletion cannot resolve those  :(
Thanks

--- End quote ---
Sorry If I can't get your idea.
You want to get the function declaration from a "shared library"?
@christobal
I'm confused about your discussion, can you give a simple test case? or where is the patch?

By the way, this thread should be moved to the CodeCompletion redesign subforum.

ivan1979:
Sorry,
i think plugin is implemented by a library (libcodecompletion.so) o no???

Navigation

[0] Message Index

[#] Next page

[*] Previous page