Software library | Wikipedia audio article
Channel: wikipedia tts
Date: 2019-01-13

This is an audio version of the Wikipedia Article:
https://en.wikipedia.org/wiki/Library_(computing)


00:04:18 1 History
00:06:28 2 Linking
00:08:23 3 Relocation
00:09:18 4 Static libraries
00:10:30 5 Shared libraries
00:12:20 5.1 Memory sharing
00:14:30 5.2 Dynamic linking
00:16:18 5.3 Optimizations
00:17:28 5.4 Locating libraries at run time
00:19:26 5.4.1 Microsoft Windows
00:20:27 5.4.2 OpenStep
00:20:58 5.4.3 Unix-like systems
00:22:16 5.5 Dynamic loading
00:23:42 6 Object and class libraries
00:28:07 7 Remote libraries
00:29:28 8 Code generation libraries
00:30:03 9 File naming
00:30:12 9.1 Most modern Unix-like systems
00:31:23 9.2 macOS
00:32:27 9.3 Microsoft Windows
00:33:38 10 See also



Listening is a more natural way of learning, when compared to reading. Written language only began at around 3200 BC, but spoken language has existed long ago.

Learning by listening is a great way to:
- increases imagination and understanding
- improves your listening skills
- improves your own spoken accent
- learn while on the move
- reduce eye strain

Now learn the vast amount of general knowledge available on Wikipedia through audio (audio article). You could even learn subconsciously by playing the audio while you are sleeping! If you are planning to listen a lot, you could try using a bone conduction headphone, or a standard speaker instead of an earphone.

Listen on Google Assistant through Extra Audio:
https://assistant.google.com/services/invoke/uid/0000001a130b3f91
Other Wikipedia audio articles at:
https://www.youtube.com/results?search_query=wikipedia+tts
Upload your own Wikipedia articles through:
https://github.com/nodef/wikipedia-tts
Speaking Rate: 0.7623247982348902
Voice name: en-US-Wavenet-F


"I cannot teach anybody anything, I can only make them think."
- Socrates


SUMMARY
=======
In computer science, a library is a collection of non-volatile resources used by computer programs, often for software development. These may include configuration data, documentation, help data, message templates, pre-written code and subroutines, classes, values or type specifications. In IBM's OS/360 and its successors they are referred to as partitioned data sets.
A library is also a collection of implementations of behavior, written in terms of a language, that has a well-defined interface by which the behavior is invoked. For instance, people who want to write a higher level program can use a library to make system calls instead of implementing those system calls over and over again. In addition, the behavior is provided for reuse by multiple independent programs.  A program invokes the library-provided behavior via a mechanism of the language.  For example, in a simple imperative language such as C, the behavior in a library is invoked by using C's normal function-call.  What distinguishes the call as being to a library function, versus being to another function in the same program, is the way that the code is organized in the system.
Library code is organized in such a way that it can be used by multiple programs that have no connection to each other, while code that is part of a program is organized to be used only within that one program.  This distinction can gain a hierarchical notion when a program grows large, such as a multi-million-line program.  In that case, there may be internal libraries that are reused by independent sub-portions of the large program.  The distinguishing feature is that a library is organized for the purposes of being reused by independent programs or sub-programs, and the user only needs to know the interface and not the internal details of the library.
The value of a library lies in the reuse of the behavior.  When a program invokes a library, it gains the behavior implemented inside that library without having to implement that behavior itself. Libraries encourage the sharing of code in a modular fashion, and ease the distribution of the code.
The behavior implemented by a library can be connected to the invoking program at different program lifecycle phases.  If the code of the library is accessed during the build of the invoking program, then the library is called a static library.  An alternative is to build the executable of the invoking program and distribute that, independently of the library implementation.  The library behavior is connected after the executable has been invoked to be executed, either as part of the process of starting the execution, or in the middle of execution.  In this case the library is called a dynamic library (loaded at run time).  A dynamic library can be loaded and linked when preparing a program for execution, by the linker.  Alternatively, in the middle of execution, an application may explicitly request that a module be loaded.
Most compiled languages have a standard library although programmers can also create their own custom libraries. Most modern software systems provide libraries that implement  ...