[issue9086] Wrong linking terminology in windows FAQ

Georg Brandl added the comment: Okay, I removed mention of static linking and used John's terms "load-time" and "run-time" linking in r85618. I also removed the note that pythonXY.dll is only needed in one case, since it's not true. -- nosy: +georg.brandl resolution: -> fixed status

[issue9086] Wrong linking terminology in windows FAQ

Martin v. Löwis added the comment: I agree with John: this paragraph is technically incorrect. See http://msdn.microsoft.com/en-us/library/ms681914%28v=VS.85%29.aspx for an "official" definition of the relevant terms. I vaguely recall objecting to that text when it got added, but in the disc

[issue9086] Wrong linking terminology in windows FAQ

Terry J. Reedy added the comment: 3.1 docs say same. For *nix, I would agree with your view of 'static', but perhaps MS uses a different terminology. Martin? Or maybe the doc writer is using a local def of static simply as a terse, if potentially confusing, alternative to 'load-time linking'.

[issue9086] Wrong linking terminology in windows FAQ

Changes by Stefan Krah : -- nosy: +skrah ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/

[issue9086] Wrong linking terminology in windows FAQ

New submission from John Miller : The 'How can I embed Python' section in the 'Python on Windows FAQ' (http://docs.python.org/faq/windows.html) uses wrong terms: What the FAQ calls static linking and dynamic linking are actally two forms of dynamic linking - load-time dynamic linking and run-ti