This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Thu 21 Aug 2014 09:15:35 Joel Brobecker wrote: > > > [If this were gdb one might want a "." followed by two spaces here, > > > but this isn't gdb. Lucky you. :-)] > > > > that's enforced in new code (which psim is anything but). i'd have no > > problem if someone felt like going through and cleaning that > > particular issue up in the whole code base. > > > > sim should be following GNU style conventions. i dislike them, but > > it's part of a larger GNU project, so deviating anyways would be bad > > form :). > > Interestingly, I have always considered sim to be part of the GDB > project, and therefore under GDB coding style. aren't they the same thing ? i guess let's see. gdb/CONTRIBUTE says: o Coding Standards All contributions must conform to the GNU Coding Standard. Submissions which do not conform to the standards will be returned with a request to reformat the changes. which is what i thought ... but then there's this follow up: GDB has certain additional coding requirements. Those requirements are explained in the GDB internals documentation in the gdb/doc directory. except there's no gdbint.texinfo anymore. let's check the website: https://www.gnu.org/software/gdb/documentation/ GDB Internals Manual (wiki only) https://sourceware.org/gdb/wiki/InternalsManual https://sourceware.org/gdb/wiki/Internals%20GDB-C-Coding-Standards ok, i guess there's a few more rules here. having the sim follow those is fine. -mike
Attachment:
signature.asc
Description: This is a digitally signed message part.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |