Am 23.04.2012 22:20, schrieb Bernd:
I have something like this:
var
some_external_func: function(foo: bar): baz; cdecl;
some_external_proc: procedure(bla: blub); cdecl;
and later I will assign them with pointers received with
GetProcAddress() from a dynamically loaded library. There are a lot of
these functions and I need to call most of them a lot of times all
over my code. It all works perfectly well with only one little
annoyance: Whenever I invoke the code completion when writing a
function call it will complete like a "normal" variable:
some_external_func :=
I have to backspace and remove the := manually so I can proceed with
the opening bracket. From this moment on everything is ok again, with
Ctrl+Schift+Space I will have a calltip hint exactly like with normal
functions. The problem is only the autocompletion.
Is this intentional? At least in my current case in 90% of all times
when I start typing the name of a procedure variable I actually want
to call it. (actually in my current project I don't even assign them
all individually with := anymore either, I have factored this one
assignment out to a place where I don't have to touch it anymore, so
its actually 99.9%)
Would it be possible to change the behavior of autocomplete for
procedure variables (maybe even make it a config option with) or would
this be considered as a wontfix because other uses happen more often
than my special case here?
Your case is not so special... the same happens e.g. when using OpenGL
functions which are procedural variables as well.
Regards,
Sven
--
_______________________________________________
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
