Hide protected/private members from completion?

[Milian Wolff]

Am Freitag 09 Januar 2009 schrieb Andreas Pakulat:
> Hi,
>
> Should we hide protected/private members from the code-completion list when
> they can't be used in a certain context? For example here:
>
> class test{ int b; }
>
> test a;
> a.<ctrl+space>
>
> Or is that too much work for too little gain (default case as above, friend
> declarations, public-private defines)?

I'd love to see that feature as it introduces a sort of error-checking before 
compiling. When I'd write something like that I'd expect KDevelop to mark it 
as an error nonetheless, so why should it suggest it as a completion?

-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20090109/54a1328e/attachment.sig>