Talk:Executable and Linkable Format
Module:WikiProject banner/doc
This page is a soft redirect.
 | This template has been replaced by Module:WikiProject banner |
Mac OS X using ELF?
Does Mac OS X use ELF?? -- Michael
- See Talk:Mac OS X. Dysprosia 07:50, 30 Sep 2003 (UTC)
In-process vs. out-of-process object sharing
I thin also this should reference OLE Object linking and embedding, which I think may embody the MS way and Maybe Component Object Model Where the *nix way is more of a Process model or some such. Quinobi 21:19, 9 July 2005 (UTC)
- Executable image formats have nothing to do with object linking models. One could implement OLE and COM using ELF (and COM objects can be "in-process", linked into the address space of the calling process, or "out of process", running in a separate address space in a separate process); I'm not sure what "the *nix way is more of a Process model or some such" means, but if you're referring to pipelines, that can be implemented with the Windows Portable Executable format and, in fact, if the Windows NT command interpreter implements the pipe operator by building a Unix-style pipeline, somebody, namely Microsoft, did implement pipelines with processes running code in PE format. Guy Harris 23:02, 17 November 2006 (UTC)
sources
free ELF object file access library might want to change to this link, old link redirects to here!
Jacksum
If ELF-32 indeed means the checksum used by this executable format, then it might make sense to add this link (and some explanation):
- Jacksum — by Dipl.-Inf. (FH) Johann N. Löfflmann in Java. Various message verification functions. Released under the GPL.
Otherwise, please correct the Jacksum article. Shinobu 16:47, 24 October 2005 (UTC)
outperform != not a competitor
This sentence doesn't make sense:
Because other formats are proprietary, platform-specific, or less extensible than ELF, some users hold that ELF outperforms other formats, whereas others may consider it a competitor to the other format
I can't tell what is trying to be said. Are we suggesting that some people think that ELF's openness and flexibility make it far beyond the alternatives (to the extent that the alternatives are not options, but relics)? Even if so, the sentence doesn't read well. The first part does not contradict the second (as expected when using whereas). One competitor may outperform the alternatives.
How about something more like: Since it is nonproprietary, platform-agnostic, and extensible, many users consider ELF to be far beyond its competitors.
Or perhaps remove the line entirely.
ELF Problems
Someone should add a section about ELF's significant problems, especially regarding dynamic linking semantics. See: [1] and [2] —The preceding unsigned comment was added by 131.111.243.37 (talk • contribs) 10:10, 13 November 2006 (UTC).
- See also Porting UNIX/Linux applications to Mac OS X: Understanding Two-Level Namespaces and Mac OS X Developer Release Notes: Two-Level Namespace Executables, as perhaps what the ELF section of the "Linux Problems" page of the Autopackage Wiki calls "hash" sometimes has ingredients that don't taste too bad, even if the hash as a whole isn't to your taste. Guy Harris 00:10, 14 November 2006 (UTC)