Talk:Shared library

This subarticle is kept separate from the main article, Library (computing), due to size or style considerations.

What is dubious about (some of the) dynamic shared libraries being linked at runtime?[edit]

I have no clue who marked this as dubious, but it should be removed.
All major operating systems support dynamic loading (and therefore linking) of modules at runtime.
Now even linking of relocations is often postponed as well, the routine is linked when it is called the first time. 107.197.102.10 (talk) 04:43, 21 October 2023 (UTC)[reply]

Some issues IMO[edit]

I'm confused about the intent of this article. Is this focused on *nix? If not, then 'shared object' is not really an aka for shared library. It's the name of the implementation of shared library in *nix environments ... just as DLL is the implementation name in Windows. I guess you could say shared object is an aka ... but then so is DLL ... and any other implementation name out there. I suggest simplify: remove 'shared object' from the first line. Include it later when ready to talk about DLL.

The stuff of about linking is very technical and hard to understand and therefore does not belong in the lead.

Stuff about executable file formats in the lead seems ham-handed.

Stuff about stack-based data is also too techy and hard to understand for the lead.

I'll work on this later. Stevebroshar (talk) 13:22, 25 April 2024 (UTC)[reply]