This page was produced by an automated import process, and may have formatting errors; feel free to fix.

Obsoleting code

Before anything else, poke the other developers (and around the source code) to see if there is anything that can be removed from GDB (an old target, an unused file).

Obsolete code is identified by adding an OBSOLETE prefix to every line. Doing this means that it is easy to identify something that has been obsoleted when greping through the sources.

The process is done in stages — this is mainly to ensure that the wider GDB community has a reasonable opportunity to respond. Remember, everything on the Internet takes a week.

  1. Post the proposal on [mailto:gdb@sourceware.org the GDB mailing list] Creating a bug report to track the task’s state, is also highly recommended.

  2. Wait a week or so.
  3. Post the proposal on [mailto:gdb-announce@sourceware.org the GDB Announcement mailing list].

  4. Wait a week or so.
  5. Go through and edit all relevant files and lines so that they are prefixed with the word OBSOLETE.

  6. Wait until the next GDB version, containing this obsolete code, has been released.
  7. Remove the obsolete code.

Maintainer note: While removing old code is regrettable it is hopefully better for GDB’s long term development. Firstly it helps the developers by removing code that is either no longer relevant or simply wrong. Secondly since it removes any history associated with the file (effectively clearing the slate) the developer has a much freer hand when it comes to fixing broken files.

None: Internals Obsoleting-code (last edited 2013-08-20 23:41:06 by StanShebs)

All content (C) 2008 Free Software Foundation. For terms of use, redistribution, and modification, please see the WikiLicense page.