Revisions to What is an application binary interface (ABI)?

added 34 characters in body

Source Link

edited Sep 26, 2022 at 18:48

35.1k
10
235
251

Application Binary Interface(ABI)

ABI - Application Binary Interface is about a machine code communication in runtime between two binary parts like - application, library, OS... ABI describes how objects are saved in memory, how functions are called(calling convention), mangling...

A good example of API and ABI is iOS ecosystem with Swift language from v5.

Application layer - When you create an application using different languages. For example you can create application using Swift and Objective-C^{[Mixing Swift and Objective-C]}
Application - OS layer - runtime - Swift Standard Library and Swift Run Time Library^[About] are parts of OS and they should not be included into each bundle(e.g. app, framework). It is the same as like Objective-C uses. Available from iOS v12.2
Library layer - Module Stability case - compile time - you will be able to import a framework which was built with another version of Swift's compiler. It means that it is safety to create a closed-source(pre-build) binary which will be consumed by a different version of compiler( .swiftinterface is used with .swiftmodule^[About]) and you will not get
```
Module compiled with _ cannot be imported by the _ compiler
//or
Compiled module was created by a newer version of the compiler
```
Library layer - Library Evolution case
1. Compile time - if a dependency was changed, a client has not to be recompiled.
2. Runtime - a system library or a dynamic framework can be hot-swapped by a new one.

[API vs ABI]
[Swift Module Stability and Library Stability]

Application Binary Interface(ABI)

ABI - Application Binary Interface is about a machine code communication in runtime between two binary parts like - application, library, OS... ABI describes how objects are saved in memory, how functions are called(calling convention), mangling...

A good example of API and ABI is iOS ecosystem with Swift language.

Application layer - When you create an application using different languages. For example you can create application using Swift and Objective-C^{[Mixing Swift and Objective-C]}
Application - OS layer - runtime - Swift Standard Library and Swift Run Time Library^[About] are parts of OS and they should not be included into each bundle(e.g. app, framework). It is the same as like Objective-C uses
Library layer - Module Stability case - compile time - you will be able to import a framework which was built with another version of Swift's compiler. It means that it is safety to create a closed-source(pre-build) binary which will be consumed by a different version of compiler( .swiftinterface is used with .swiftmodule^[About]) and you will not get
```
Module compiled with _ cannot be imported by the _ compiler
//or
Compiled module was created by a newer version of the compiler
```
Library layer - Library Evolution case
1. Compile time - if a dependency was changed, a client has not to be recompiled.
2. Runtime - a system library or a dynamic framework can be hot-swapped by a new one.

[API vs ABI]
[Swift Module Stability and Library Stability]

Application Binary Interface(ABI)

ABI - Application Binary Interface is about a machine code communication in runtime between two binary parts like - application, library, OS... ABI describes how objects are saved in memory, how functions are called(calling convention), mangling...

A good example of API and ABI is iOS ecosystem with Swift language from v5.

Application layer - When you create an application using different languages. For example you can create application using Swift and Objective-C^{[Mixing Swift and Objective-C]}
Application - OS layer - runtime - Swift Standard Library and Swift Run Time Library^[About] are parts of OS and they should not be included into each bundle(e.g. app, framework). It is the same as like Objective-C uses. Available from iOS v12.2
Library layer - Module Stability case - compile time - you will be able to import a framework which was built with another version of Swift's compiler. It means that it is safety to create a closed-source(pre-build) binary which will be consumed by a different version of compiler( .swiftinterface is used with .swiftmodule^[About]) and you will not get
```
Module compiled with _ cannot be imported by the _ compiler
//or
Compiled module was created by a newer version of the compiler
```
Library layer - Library Evolution case
1. Compile time - if a dependency was changed, a client has not to be recompiled.
2. Runtime - a system library or a dynamic framework can be hot-swapped by a new one.

[API vs ABI]
[Swift Module Stability and Library Stability]

added 10 characters in body

Source Link

edited Sep 26, 2022 at 17:52

yoAlex5

35.1k
10
235
251

Application Binary Interface(ABI)

ABI - Application Binary Interface is about a machine code communication in runtime between two binary parts like - application, library, OS... ABI describes how objects are saved in memory, how functions are called(calling convention), mangling...

A good example of API and ABI is iOS ecosystem with Swift language.

Application layer - When you create an application using different languages. For example you can create application using Swift and Objective-C^{[Mixing Swift and Objective-C]}
Application - OS layer - runtime - Swift runtimeStandard Library and standardSwift librariesRun Time Library^[About] are parts of OS and they should not be included into each bundle(e.g. app, framework). It is the same as like Objective-C uses
Library layer - Module Stability case - compile time - you will be able to import a framework which was built with another version of Swift's compiler. It means that it is safety to create a closed-source(pre-build) binary which will be consumed by a different version of compiler( .swiftinterface is used with .swiftmodule^[About]) and you will not get
```
Module compiled with _ cannot be imported by the _ compiler
//or
Compiled module was created by a newer version of the compiler
```
Library layer - Library Evolution case
1. Compile time - if a dependency was changed, a client has not to be recompiled.
2. Runtime - a system library or a dynamic framework can be hot-swapped by a new one.

[API vs ABI]
[Swift Module Stability and Library stability]Stability]

Application Binary Interface(ABI)

ABI - Application Binary Interface is about a machine code communication in runtime between two binary parts like - application, library, OS... ABI describes how objects are saved in memory, how functions are called(calling convention), mangling...

A good example of API and ABI is iOS ecosystem with Swift language.

Application layer - When you create an application using different languages. For example you can create application using Swift and Objective-C^{[Mixing Swift and Objective-C]}
Application - OS layer - runtime - Swift runtime and standard libraries are parts of OS and they should not be included into each bundle(e.g. app, framework). It is the same as like Objective-C uses
Library layer - Module Stability case - compile time - you will be able to import a framework which was built with another version of Swift's compiler. It means that it is safety to create a closed-source(pre-build) binary which will be consumed by a different version of compiler( .swiftinterface is used with .swiftmodule^[About]) and you will not get
```
Module compiled with _ cannot be imported by the _ compiler
//or
Compiled module was created by a newer version of the compiler
```
Library layer - Library Evolution case
1. Compile time - if a dependency was changed, a client has not to be recompiled.
2. Runtime - a system library or a dynamic framework can be hot-swapped by a new one.

[API vs ABI]
[Swift Module and Library stability]

Application Binary Interface(ABI)

ABI - Application Binary Interface is about a machine code communication in runtime between two binary parts like - application, library, OS... ABI describes how objects are saved in memory, how functions are called(calling convention), mangling...

A good example of API and ABI is iOS ecosystem with Swift language.

Application layer - When you create an application using different languages. For example you can create application using Swift and Objective-C^{[Mixing Swift and Objective-C]}
Application - OS layer - runtime - Swift Standard Library and Swift Run Time Library^[About] are parts of OS and they should not be included into each bundle(e.g. app, framework). It is the same as like Objective-C uses
Library layer - Module Stability case - compile time - you will be able to import a framework which was built with another version of Swift's compiler. It means that it is safety to create a closed-source(pre-build) binary which will be consumed by a different version of compiler( .swiftinterface is used with .swiftmodule^[About]) and you will not get
```
Module compiled with _ cannot be imported by the _ compiler
//or
Compiled module was created by a newer version of the compiler
```
Library layer - Library Evolution case
1. Compile time - if a dependency was changed, a client has not to be recompiled.
2. Runtime - a system library or a dynamic framework can be hot-swapped by a new one.

[API vs ABI]
[Swift Module Stability and Library Stability]

added 78 characters in body

Source Link

edited Apr 20, 2021 at 17:22

yoAlex5

35.1k
10
235
251

Application Binary Interface(ABI)

ABI - Application Binary Interface is about a machine code communication in runtime between two binary parts like - application, library, OS... ABI describes how objects are saved in memory, how functions are called(calling convention), mangling...

A good example of API and ABI is iOS ecosystem with Swift language.

Application layer - When you create an application using different languages. For example you can create application using Swift and Objective-C^{[Mixing Swift and Objective-C]}
Application - OS layer - runtime - Swift runtime and standard libraries are parts of OS and they should not be included into each bundle(e.g. app, framework). It is the same as like Objective-C uses
Library layer - Module Stability case - compile time - you will be able to import a framework which was built with another version of Swift's compiler. It means that it is safety to create a closed-source(pre-build) binary which will be consumed by a different version of compiler( .swiftinterface is used with .swiftmodule^[About]) and you will not get
```
Module compiled with _ cannot be imported by the _ compiler
//or
Compiled module was created by a newer version of the compiler
```
Library layer - Library Evolution case
1. Compile time - if a dependency was changed, a client has not to be recompiled.
2. Runtime - a system library or a dynamic framework can be hot-swapped by a new one.

[API vs ABI]
[Swift Module and Library stability]

Application Binary Interface(ABI)

ABI - Application Binary Interface is about a machine code communication in runtime between two binary parts like - application, library, OS... ABI describes how objects are saved in memory, how functions are called(calling convention), mangling...

A good example of API and ABI is iOS ecosystem with Swift language.

Application layer - When you create an application using different languages. For example you can create application using Swift and Objective-C^{[Mixing Swift and Objective-C]}
Application - OS layer - runtime - Swift runtime and standard libraries are parts of OS and they should not be included into each bundle(e.g. app, framework). It is the same as like Objective-C uses
Library layer - Module Stability case - compile time - you will be able to import a framework which was built with another version of Swift's compiler. It means that it is safety to create a closed-source(pre-build) binary which will be consumed by a different version of compiler( .swiftinterface is used with .swiftmodule^[About]) and you will not get
```
Module compiled with _ cannot be imported by the _ compiler
```
Library layer - Library Evolution case
1. Compile time - if a dependency was changed, a client has not to be recompiled.
2. Runtime - a system library or a dynamic framework can be hot-swapped by a new one.

[API vs ABI]
[Swift Module and Library stability]

Application Binary Interface(ABI)

ABI - Application Binary Interface is about a machine code communication in runtime between two binary parts like - application, library, OS... ABI describes how objects are saved in memory, how functions are called(calling convention), mangling...

A good example of API and ABI is iOS ecosystem with Swift language.

Application layer - When you create an application using different languages. For example you can create application using Swift and Objective-C^{[Mixing Swift and Objective-C]}
Application - OS layer - runtime - Swift runtime and standard libraries are parts of OS and they should not be included into each bundle(e.g. app, framework). It is the same as like Objective-C uses
Library layer - Module Stability case - compile time - you will be able to import a framework which was built with another version of Swift's compiler. It means that it is safety to create a closed-source(pre-build) binary which will be consumed by a different version of compiler( .swiftinterface is used with .swiftmodule^[About]) and you will not get
```
Module compiled with _ cannot be imported by the _ compiler
//or
Compiled module was created by a newer version of the compiler
```
Library layer - Library Evolution case
1. Compile time - if a dependency was changed, a client has not to be recompiled.
2. Runtime - a system library or a dynamic framework can be hot-swapped by a new one.

[API vs ABI]
[Swift Module and Library stability]

added 158 characters in body

Source Link

edited Apr 6, 2021 at 15:17

yoAlex5

35.1k
10
235
251

Loading

added 41 characters in body

Source Link

edited Mar 27, 2021 at 16:11

yoAlex5

35.1k
10
235
251

Loading

added 6 characters in body

Source Link

edited Feb 5, 2021 at 9:47

yoAlex5

35.1k
10
235
251

Loading

added 103 characters in body

Source Link

edited Aug 7, 2020 at 15:54

yoAlex5

35.1k
10
235
251

Loading

added 24 characters in body

Source Link

edited Aug 7, 2020 at 14:22

yoAlex5

35.1k
10
235
251

Loading

edited body

Source Link

edited Aug 7, 2020 at 14:12

yoAlex5

35.1k
10
235
251

Loading

added 10 characters in body

Source Link

edited Jul 23, 2020 at 14:45

yoAlex5

35.1k
10
235
251

Loading

deleted 1 character in body

Source Link

edited Jul 23, 2020 at 10:36

yoAlex5

35.1k
10
235
251

Loading

deleted 4 characters in body

Source Link

edited Jun 16, 2020 at 9:54

yoAlex5

35.1k
10
235
251

Loading

added 2 characters in body

Source Link

edited Jun 6, 2020 at 7:01

yoAlex5

35.1k
10
235
251

Loading

added 30 characters in body

Source Link

edited Apr 10, 2020 at 12:25

yoAlex5

35.1k
10
235
251

Loading

added 469 characters in body

Source Link

edited Apr 4, 2020 at 18:59

yoAlex5

35.1k
10
235
251

Loading

added 644 characters in body

Source Link

edited Dec 10, 2019 at 16:00

yoAlex5

35.1k
10
235
251

Loading

Source Link

answered Dec 10, 2019 at 15:52

yoAlex5

35.1k
10
235
251

Loading

Collectives™ on Stack Overflow

Return to Answer