[development] Drupal Function Frequency Report?
Robert Douglass
rob at robshouse.net
Sun Jun 29 11:49:22 UTC 2008
Yeah, that's the one. I had this set up once but have deleted it
since. It's a funny story actually. I configured it to keep logs of my
local Drupal, but forgot to turn it off. Several weeks later my hard
drive was completely out of space and crashing. It wasn't until I
found the 120GB of KCacheGrind files that I could use my computer again.
Robert Douglass
Senior Drupal Advisor
Acquia
robert at acquia.com
+1 517 639 0204 (US)
+49 228 4097 197 (Germany)
On Jun 29, 2008, at 1:39 PM, Marjorie Roswell wrote:
> Is that this?
> http://kcachegrind.sourceforge.net/cgi-bin/show.cgi
>
> I seriously wouldn't have a clue how to get that running.
>
> If it's easy for you, can you release this report? If not, well, 'twas
> a good idea, anyhow.
>
> Margie
>
> On Sun, Jun 29, 2008 at 7:09 AM, Robert Douglass <rob at robshouse.net>
> wrote:
>> XCachGrind makes such reports.
>>
>> Robert Douglass
>>
>> Senior Drupal Advisor
>> Acquia
>> robert at acquia.com
>> +1 517 639 0204 (US)
>> +49 228 4097 197 (Germany)
>>
>>
>>
>> On Jun 29, 2008, at 1:04 PM, Marjorie Roswell wrote:
>>
>>> I'm on a drupal learning curve.
>>>
>>> It occurs to me that I'd love to see a report of all the functions
>>> used in Drupal by frequency. (Then, I'd tackle the learning curve by
>>> starting with what's used most, and moving down the list!)
>>>
>>> I imagine starting with something like the api pull from the Module
>>> Builder Module (http://drupal.org/project/module_builder) and then
>>> somehow scanning the CVS for all the functions, and calculating a
>>> frequency.
>>>
>>> Seriously, would love to basically tackle this learning curve in a
>>> logical way, based on how often something appears in code, ideally
>>> in
>>> both core and contrib, combned.
>>>
>>> I recognize that little-used code functions may still be quite
>>> important, but this approach would certainly serve as a good guide.
>>>
>>> I don't have the skillset to write this report. Is there anyone for
>>> whom producing this function frequency report would be a relative
>>> cinch?
>>>
>>> Margie
>>
>>
More information about the development
mailing list