Uploaded by kaushikshivam74

ans 2

advertisement
Management of library
compiler
A
compiler is aspecial program that
translates a programming language's
source code into machine code, bytecode or
another programming language. The source
code is typically written in a high-level,
human-readable language such as java, C+
+. Aprogrammer writes the source code in
a code editor or an integrated development
environment (IDE) that includes an editor,
saving the source code to one or more text
files. A compiler that supports the source
programming language reads the files,
analyzes the code, and translates it into a
format suitable for the target platform.
Compilers that translate source code
to machine code target specific operating
systems and computer architectures. This
type of output is sometimes referred toas
object code (which is not related to subject
oriented programming). The output
machine code is made up entirely of binary
bits - 1s and Os - so it can be read and
executed by the processors on the target
computers. For example, a compiler might
output machine code for the Linux x64
platform or Linux ARM 64-bit platform.
In a compiler, managing a library
entailsclassifying and managing allof the
different functions and routines used
throughout compilation. Among them are:
Creatingreusable code modules in the
source language that can be linked into
programmes during compilation is known
as library collection.
Ina compiler, managing a library entails
classifying andmanaging all of the
different functions and routines used
throughout compilation. Amongthem are:
Creating reusable code modules in the
source language that can be linked into
programmes during compilation is known
as library collection.
Version control is the process of keeping
severalversions of library modules to
address upgrades, bug patches,and
compatibility problems.
Documentation: Producing and updating
documentation for library functions to help
developers make the most use of them.
Monitoring interlibrary dependencies to
guarantee proper linking during compilation
is known as dependency tracking.
Testing and quality control: Continually
address upgrades, bug patches, and
compatibility problems.
Documentation:Producing and updating
documentation for library functions to help
developers make the most use of them.
Monitoring interlibrary dependencies to
guarantee proper linking during compilation
is known as dependency tracking.
Testing and quality control: Continually
checking that library functions fulfil
performance requirements and operate as
intended.
Implementing security mechanisms to
preserve the confidentiality and integrity of
library code.
Download