It would be great to be able to right click on a function declaration and be able to "show all calls to this function" which would then list all the other places in the code (with file and line #) where this function is being called..

It's sort of a reverse ctrl+click on function, which takes you to the declaration.

To clarify, upon right clicking a function the context menu that appears should contain a list of calls to that function... When clicking on one of them, it'll open the place where the function is declared..

+1
This would be an amazing feature, and would bring the IDE up to speed with the functionality of some of the "typed language" IDEs.

For complex projects, this is like having an extra sense (a gift!) that makes understanding a project much easier. It makes navigating a project easier as you can simply jump to the caller of a function/member/class without searching for it.

I would love such a feature. Right now I'm reduced to doing lots of global searches for the uses of a function.

Yeah,

"Search in files" is sometimes (on a bad day) the most used function for me. ( alt f7 )! Would be lost without it! Having said that, I'd love to use it less, and I am mainly using it to "backtrace" through code...

If you've never used a "called by, used by" feature - you don't know what you're missing.

I wonder if that visualstudio based product "vs php" can do it seeing it is built on vs? That would be at least an instance of it's possibility.
(will this post be deleted for mentioning a competitor product?)

I know this feature from other editor and I was looking for it. Since I'm a new user I thought that I just did not find it but it must be there.
Now I understand that there is no need to look for it and stick to Alt-F7

I would also like to right click and select 'find usage...'

Ernest

+1

+1

I think this is not possible for a PHP language which is weak-type to find all the method calls in code.
But maybe PHPEd developers will find a possibility for it.

bump.

@ mikhailt

PHP has had a Reflection API for ages, see:

http://php.net/manual/en/book.reflection.php
http://php.net/manual/en/class.reflectionclass.php



It is more than capable of creating a complete code mapping for a project.
It may not be the tool for this particular problem, but it does demonstrate that it is possible for code to be "introspective"!

I'd say whether or not the feature exists is all about the demand expressed by users, and how it ranks in importance.