Talk:Object code

Merger proposal

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.

The result of this discussion was to not merge. —Nils von Barth (nbarth) (talk) 14:23, 3 May 2013 (UTC)

---

It has been proposed that this article be merged into Object file.

• Oppose. An object file is a container for object code, not the same as the thing contained. Object code, and its differences from source and executable code, is a legitimate subject. An object file or library is of less interest, and may only have transient existence as a vehicle for feeding the object code from the compiler into the linkeditor to create the executable. It would be more reasonable to merge some of the content from Object file into this article, but sources should be cited. Aymatth2 (talk) 00:42, 2 June 2012 (UTC)

• Oppose for sure. Totally different ball park. History2007 (talk) 09:18, 16 June 2012 (UTC)

• Oppose, as object code is also a legal term e.g. in ESA contracts. 153.96.89.3 (talk) 14:21, 4 July 2012 (UTC)

• Oppose. Object files are not object code. However, the article is a stub. Maybe just improve it or something. — Preceding unsigned comment added by 205.222.248.28 (talk) 13:54, 7 September 2012 (UTC)

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

To summarize the discussion as I understand it:

Object code is the output of a compiler, often machine code, but also an intermediate language.

An object file is a file containing or wrapping object code, but may contain other data besides. In some cases “object file” is used narrowly for files that are not themselves executable or libraries, while in other cases it’s used broadly to include executables and libraries.

—Nils von Barth (nbarth) (talk) 14:35, 3 May 2013 (UTC)