Static linking means that the source code inside the library will be literally copy-pasted into your application binary. When you use a library you can choose between two approaches. So, last time, you know, when we talked about the Swift compiler and linker, I mentioned, that they can resolve dependencies in your program.
Oh wait, there is a bug in the lib, how can I fix it? Well, this is where things get a bit complicated, but don't worry too much, I'll try to explain how it works. This way you can outsource Swift code into a separate file (or bunch of files), throw in some access control to allow other apps to use public methods and call functions from your library and here we go, we just shared our common code between our applications. A shared library is a special kind of binary component that you can use in your main application. 🧠įortunately computer programmers faced the exact same issue, so they invented shared libraries. Well, this could work of course, but what happens if you discover a bug in the pluralization component? Now you have to fix the issue at two places, since you've just duplicated the entire stuff. The first thing that can cross your mind is to copy all the source code from the first application into the second one.
In your next application, you face the exact same issue, you have to print countable items (e.g 2 bananas). It works great, you finish the app and you start working on your next one. Imagine that you are creating a simple application to pluralize a string. A library is a collection of Swift components that other applications can use.
0 kommentar(er)
