int (bar_not_visible)();
int bar_visible();
void foo()
{
ba|Ctrl+Space
}
code completion (for ba ) suggests only bar_visible, and not bar_not_visible.
It is an uncommon style, but I think it is valid.
In short, when you declare a callback, you declare a function pointer. So, a pointer which know the address of a function (I know that you perfectly know that, I am just going step by step to make things clear as best as I can).
For a classic variable, we use this:
For a classic pointer:
int *pfoo;[code]
For function pointers:
[code]int (*pbar)(void);
So there are no reasons to think removing the pointer operand is not legal.
In fact, we could probably say that removing parenthesis is just a shortcut for easier read, and the parenthesis write is the good one.
To conclude, I have tried a very little program (which do nothing) and compiled it with "gcc foo.c -ansi" and it gaves me no error or warning.
Here it is:
int (bar_not_v)();
int (bar_v)();
void main()
{
bar_v();
bar_not_v();
}
int bar_not_v()
{
}
int (bar_v)()
{
}
[/code][/code]
Oh, the way i expressed has some wrong, i mean the code completion cannot list the functions of lua's C API.
i am doing a lua binding library for c++, so i often need to call the lua's C API to achieve some features :P
Still not clear about your idea. If you would like to show C API, should should have C code parsed by the CC's parser. Where is you C API declaration? Please give more details.
the C API declarations are in the Lua's header files
for example:
// in lua.h
LUA_API lua_State *(lua_newstate) (lua_Alloc f, void *ud);