Bugs 38840+39596: Coverage analysis and static analysis: Whats next ?
John Smith
lbalbalba at gmail.com
Thu Sep 6 04:15:07 PDT 2012
On Wed, Sep 5, 2012 at 1:15 PM, Michael Meeks <michael.meeks at suse.com> wrote:
>
>
> Of course, if you really don't want to look into / learn that; I had
> another idea that'd be great to get implemented:
>
> https://bugs.freedesktop.org/show_bug.cgi?id=39439
>
Alright, let me see if I understand this one correctly first. You
basically want people to be able to find out what gets "#define" 'd in
what rc files ? So for example, you want people to search for
"FL_RECORD" to discover that that gets defined in
'./sw/source/ui/envelp/mailmrge.hrc" ?
If that is true, I guess I could work on a shell script that does
something like this :
find /usr/local/src/libreoffice -name \*.\?rc -exec grep "FL_RECORD" {} \;
of course, those searches will take a while and will have to be
executed on the Linux cmd prompt, so that will be no good for Windows
users.
But again, I feel things similar to this must have been done before
elsewhere. Arent there program around that tell you what gets #define
'd in which /usr/include header files ? Dont some IDE's even do stuff
like that for you automagically ? Surely it would be far easier to
modify such logic to work on those *.?rc files than to start from
scratch completely ?
- John Smith.
More information about the LibreOffice
mailing list