search

timbunce / devel-nytprof

Devel::NYTProf is a powerful feature-rich source code profiler for Perl. (Mostly in maintenance mode, so PRs are much more likely to be acted upon than Issues.)
http://blog.timbunce.org/tag/nytprof/
67 stars 51 forks source link

Dead code list #127

Closed marcespie closed 2 years ago

marcespie commented 5 years ago

I just used NYTProf to GC old code after some major refactor.

It was slightly painful, as you mostly have to read thru files and see lines which are left blankly annotated.

I was wondering about the possibility to add a list/some coloring of methods which are NOT called in the profile at hand. This would have come in handy in my case.

jkeenan commented 3 years ago

I just used NYTProf to GC old code after some major refactor.

It was slightly painful, as you mostly have to read thru files and see lines which are left blankly annotated.

I was wondering about the possibility to add a list/some coloring of methods which are NOT called in the profile at hand. This would have come in handy in my case.

If your objective is to identify code which is no longer needed, have you considered using Devel::Cover? I've long relied on that to identify code -- at least that in *.pm files -- which is not being reached and which may be removable?

Thank you very much. Jim Keenan

jkeenan commented 2 years ago

I just used NYTProf to GC old code after some major refactor. It was slightly painful, as you mostly have to read thru files and see lines which are left blankly annotated. I was wondering about the possibility to add a list/some coloring of methods which are NOT called in the profile at hand. This would have come in handy in my case.

If your objective is to identify code which is no longer needed, have you considered using Devel::Cover? I've long relied on that to identify code -- at least that in *.pm files -- which is not being reached and which may be removable?

I will close this ticket at the end of the month unless we get a response from the OP.

jkeenan commented 2 years ago

I just used NYTProf to GC old code after some major refactor. It was slightly painful, as you mostly have to read thru files and see lines which are left blankly annotated. I was wondering about the possibility to add a list/some coloring of methods which are NOT called in the profile at hand. This would have come in handy in my case.

If your objective is to identify code which is no longer needed, have you considered using Devel::Cover? I've long relied on that to identify code -- at least that in *.pm files -- which is not being reached and which may be removable?

I will close this ticket at the end of the month unless we get a response from the OP.

Closing as per schedule.