How does structure binding work in iOS?

I am looking for a detailed explanation of how wireframing works. What happens during the link phase at build time and what happens at runtime? How specifically is it not necessary to bind a framework other than the required binding? Does anyone know a link to an article that explains this?

+4
source share
1 answer

GOOD, there is nothing like a weak and strong connection in terms of linking a library or structure.

Strong and weak references for variables. See Apple Documentation

In addition, the links for the built-in libraries and user libraries are different. Also, static libraries can only be created and linked on the iPhone and without dynamic libraries.

If you are talking about library binding at the compiler level, then Apple will definitely guide you through this (binding and binding at the compiler level is the same for almost all compilers and is beyond the scope of this discussion). To link static libraries you have ways to search for change headers, add them to the target, add dependencies, etc. here is an example of creating and linking a static library

When compiling code for the first time, the compiler makes references to compiled classes in the static library and headers, and it does not compile every time if it has no changes.

0
source

Source: https://habr.com/ru/post/1412172/


All Articles