Bug 340889

Summary: Document recommended use practices for valgrind.h etc in other projects
Product: [Developer tools] valgrind Reporter: Julian Seward <jseward>
Component: generalAssignee: Julian Seward <jseward>
Status: REPORTED ---    
Severity: normal CC: mark
Priority: NOR    
Version First Reported In: 3.10 SVN   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Julian Seward 2014-11-12 13:49:25 UTC 
Per discussion on irc on 12 Nov 2014, it seems that we should encourage projects
that want to use valgrind.h, memcheck.h, etc, to #include them from system headers
and do feature checks in the "normal" (autoconfy?) ways.  And discourage projects
from actually copying the files.

* document the manual (where, though?)
* maybe change the text at the top of the files, so as to explain the new guidelines



Reproducible: Always