Bug 340889 - Document recommended use practices for valgrind.h etc in other projects
Summary: Document recommended use practices for valgrind.h etc in other projects
Status: REPORTED
Alias: None
Product: valgrind
Classification: Developer tools
Component: general (other bugs)
Version First Reported In: 3.10 SVN
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-12 13:49 UTC by Julian Seward
Modified: 2014-11-12 13:54 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
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