This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/376: #include <...> in gdb headers
- From: ac131313 at redhat dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 23 Feb 2002 18:02:01 -0000
- Subject: gdb/376: #include <...> in gdb headers
- Reply-to: ac131313 at redhat dot com
>Number: 376
>Category: gdb
>Synopsis: #include <...> in gdb headers
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Sat Feb 23 10:08:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: ac131313@redhat.com
>Release: unknown-1.0
>Organization:
>Environment:
>Description:
The coding standard indicates that each header file should include anything they refer to (typedef's typically).
It should also clarify that the header should try to avoid including system headers at any cost. Making an object opaque and only including the headers in the corresponding .c file for instance.
The rationale is that sucking in system header files is a messy business - it always breaks for someones build. By localizing it to a single .c file that risk is better managed.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: