glossery: introduce some first-use items
This requires the usage of \glsentrytext in chapters etc., because the first expansion shouldn't happen there.
This commit is contained in:
parent
c56bcd9c4b
commit
1cae6ec1ec
4 changed files with 55 additions and 31 deletions
|
@ -1,41 +1,60 @@
|
|||
% // vim: set ft=tex:
|
||||
|
||||
\newglossaryentry{Rust}{
|
||||
name=Rust
|
||||
, description={
|
||||
TODO programming language
|
||||
}
|
||||
\newglossaryentry{Rust} {
|
||||
name = {Rust},
|
||||
long = {the Rust programming language},
|
||||
description = {
|
||||
Statically typed programming language that uses a new concept of variable ownership and reference tracking. Largely explain in \autoref{context::rust}.
|
||||
},
|
||||
first = {\glsentrylong{Rust}}
|
||||
}
|
||||
|
||||
\newglossaryentry{proglang} {
|
||||
name = {programming language},
|
||||
description = {
|
||||
A well-defined language used to write software. Hundreds of language exists, each with focus on different aspects like comfort for humans, size, speed, safety, etc.
|
||||
},
|
||||
}
|
||||
|
||||
|
||||
\newglossaryentry{compiler}{
|
||||
name = compiler,
|
||||
long = {source- to machine-code compiler},
|
||||
description = {
|
||||
A program that can transform software source code to executable machine code.
|
||||
Typically targetted for a \glsentryname{proglang} or a family of \glspl{proglang}.
|
||||
},
|
||||
first = {\glsentrylong{compiler}}
|
||||
}
|
||||
|
||||
\newglossaryentry{addrspace}{
|
||||
name = memory address space,
|
||||
name = address space,
|
||||
long = bound address range in memory,
|
||||
description = {
|
||||
A logical entity that represents parts of the virtual memory, specified with a starting address and the length in a standardize unit
|
||||
A logical entity that represents a section of memory, specified with a start address and either by end address or length given in a standardize unit
|
||||
},
|
||||
first = {\glsentrylong{addrspace}}
|
||||
}
|
||||
|
||||
\newglossaryentry{API}{
|
||||
\newglossaryentry{api}{
|
||||
name = API,
|
||||
long = {Application Programming Interface},
|
||||
description = {
|
||||
Application Programming Interface
|
||||
},
|
||||
first = {\glsentrylong{api}}
|
||||
}
|
||||
|
||||
\newglossaryentry{OS}{
|
||||
name = Operating System,
|
||||
name = OS,
|
||||
long = Operating System,
|
||||
description = {
|
||||
The software that manages the system's hardware ressources.
|
||||
Other \glspl{app} can access the ressources only through the interface provided by the \gls{OS}.
|
||||
},
|
||||
first = {\glsentrylong{OS}}
|
||||
}
|
||||
|
||||
|
||||
\newglossaryentry{fs}{
|
||||
name = filesystem,
|
||||
description = {
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue