Content deleted Content added
Guy Harris (talk | contribs) →History: Yup. |
Guy Harris (talk | contribs) →How are "Microsoft Windows library files" not shared libraries?: Microsoft Windows library files says that the "system-files" are shared libraries. |
||
Line 193:
:"WinAPI does not '''force''' developers to handle low-level stuff; it '''allows''' them to do low-level stuff" Perhaps what they meant is that if you use ''only'' the Windows API, you have to do the low-level stuff yourself.
:"How is GUI related to this?" Perhaps they're saying that doing the low-level GUI stuff is more work than doing it elsewhere. But a citation for all of that would probably be called for here. [[User:Guy Harris|Guy Harris]] ([[User talk:Guy Harris|talk]]) 00:15, 14 November 2024 (UTC)
== How are "Microsoft Windows library files" not shared libraries? ==
The article currently says:
{{blockquote|Programs can access API functionality via [[Shared library|shared-library]] technologies or via [[Microsoft Windows library files|system-file]] access.}}
[[Microsoft Windows library files]] says, right at the top of the page:
{{blockquote|The [[Microsoft Windows]] [[operating system]] and [[Microsoft Windows SDK]] support a collection of [[shared libraries]] that [[software]] can use to access the [[Windows API]]. This article provides an overview of the core libraries that are included with every modern Windows [[Installation (computer programs)|installation]], on top of which most Windows [[Application software|applications]] are built.}}
So the "system-files" (or just "system files - no need for the hyphen, at least in English) are, apparently, shared libraries.
In what way are they ''not'' shared libraries? If they are shared libraries, that statement is redundant. [[User:Guy Harris|Guy Harris]] ([[User talk:Guy Harris|talk]]) 05:08, 2 February 2025 (UTC)
| |||