https://DevOpsCloud.io -- Cloud Monk Losang Jinpa

Return to 21st Century C, C Glossary

• alignment - “A requirement that data elements begin at certain boundaries in memory. For example, given an 8-bit alignment requirement, a struct holding a 1-bit char followed by an 8-bit int might need 7 bits of padding after the char so that the int starts on an 8-bit boundary.” (21cC 2014)

• ASCII - “American Standard Code for Information Interchange. A standard mapping from the naïve English character set to the numbers 0–127. Tip: on many systems, man ascii will print the table of codes.” (21cC 2014)

• automatic allocation - “For an automatically allocated variable, its space in memory is allocated by the system at the point of the variable's declaration, then removed at the end of the given scope.” (21cC 2014)

• Autotools - “A set of programs from GNU that simplify automatic compilation on any system, including Autoconf, Automake, and Libtool.” (21cC 2014)

• Benford's law - “Leading digits in a wide range of data sets tend to have a log-like distribution: 1 has about 30% frequency, 2 about 17.5%, … 9 about 4.5%.” (21cC 2014)

• Boolean - “True/false. Named after George Boole, an English mathematician living in the early-to-mid 1800s.” (21cC 2014)

• BSD - “Berkeley Software Distribution. An implementation of POSIX.” (21cC 2014)

• callback function - “A function (A) that is sent as an input to another function (B) so that function B can call function A over the course of its operation. For example, generalized sort functions typically take as input a function to compare two elements.” (21cC 2014)

• call graph - “A box-and-arrow diagram showing which functions call and are called by which other functions.” (21cC 2014)

• cetology - “The study of whales.” (21cC 2014)

• compiler - “Formally, the program that converts the (human-readable) text of a program into (human-illegible) machine instructions. Often used to refer to the preprocessor + compiler + linker.” (21cC 2014)

• debugger - “A program for interactive execution of a compiled program, allowing users to pause the program, check and modify variable values, et cetera. Often useful for understanding bugs.” (21cC 2014)

• deep copy - “A copy of a structure containing pointers, which follows all pointers and makes copies of the pointed-to data.” (21cC 2014)

• encoding - “The means by which human-language characters are converted into numeric codes for processing by the computer. See also ASCII, multibyte encoding, and wide-character encoding.” (21cC 2014)

• environment variable - “A variable present in the environment of a program, set by the parent program (typically the shell).” (21cC 2014)

• external pointer - “See opaque pointer.” (21cC 2014)

• floating point - “A representation of a number akin to scientific notation, like 2.3×10^4, with an exponent part (in this example, 4) and a mantissa (here, 2.3). After writing down the mantissa, think of the exponent allowing the decimal point to float to its correct position.” (21cC 2014)

• frame - “The space in the stack in which function information (such as inputs and automatic variables) is stored.” (21cC 2014)

• GDB - “GNU debugger.” (21cC 2014)

• global - “A variable is global when its scope is the entire program. C doesn't really have global scope, but if a variable is in a header that can reasonably be expected to be included in every code file in a program, then it is reasonable to call it a global variable.” (21cC 2014)

• glyph - “A symbol used for written communication.” (21cC 2014)

• GNU - “Gnu's Not Unix.” (21cC 2014)

• GSL - “GNU Scientific Library.” (21cC 2014)

• heap - “The space of memory from which manually allocated memory is taken. Compare with the stack.” (21cC 2014)

• IDE - “Integrated development environment. Typically a program with a graphical interface based around a text editor, with facilities for compilation, debuging, and other programmer-friendly features.” (21cC 2014)

• integration test - “A test that executes a sequence of steps that involve several segments of a code base (each of which should have its own unit test).” (21cC 2014)

• library - “Basically, a program that has no main function, and is therefore a set of functions, typedefs, and variables available for use by other programs.” (21cC 2014)

• linker - “The program that joins together disparate portions of a program (such as separate object files and libraries) and thus reconciles references to external-to-one-object-file functions or variables.” (21cC 2014)

• Linux - “Technically, an operating system kernel, but generally used to refer to a full suite of BSD/GNU/Internet Systems Consortium/Linux/Xorg/… utilities bundled as a unified package.” (21cC 2014)

• macro - “A (typically) short blob of text for which a (typically) longer blob is substituted.” (21cC 2014)

• manual allocation - “Allocation of a variable on the heap at the programmer's request, using malloc or calloc, and freed at the user's request via free.” (21cC 2014)

• multibyte encoding - “An encoding of text that uses a variable number of chars to represent a single human-language character. Contrast with wide-character encoding.” (21cC 2014)

• mutex - “Short for mutual exclusion, a structure that can be used to ensure that only one thread is using a resource at a time.” (21cC 2014)

• NaN - “Not-a-Number. The IEEE 754 (floating-point) standard defines this as the outcome of mathematical impossibilities like 0/0 or log(-1). Often used as a flag for missing or bad data.” (21cC 2014)

• object - “A data structure and the associated functions that act on the data structure. Ideally, the object encapsulates a concept, providing a limited set of entry points for other code to interact with the object.” (21cC 2014)

• object file - “A file containing machine-readable instructions. Typically the result of running a compiler on a source code file.” (21cC 2014)

• opaque pointer - “A pointer to data in a format that can't be read by the function handling the pointer, but that can be passed on to other functions that can read the data. A function in a scripting language might call one C function that returns an opaque pointer to C-side data, and then a later function in the scripting language would use that pointer to act on the same C-side data.” (21cC 2014)

• POSIX - “The Portable Operating System Interface. An IEEE standard to which UNIX-like operating systems conform, describing a set of C functions, the shell, and some basic utilities.” (21cC 2014)

• preprocessor - “Conceptually, a program that runs just before the compiler, executing directives such as #include and #define. In practice, typically a part of the compiler.” (21cC 2014)

• process - “A running program.” (21cC 2014)

• profiler - “A program that reports where your program is spending its time, so you know where to focus your efforts at speedup.” (21cC 2014)

• pthread - “POSIX thread. A thread generated using the C threading interface defined in the POSIX standard.” (21cC 2014)

• RNG - “Random number generator, where random basically means that one can reasonably expect that a sequence of random numbers is not systematically related to any other sequence.” (21cC 2014)

• RTFM - “Read the manual.” (21cC 2014)

• Sapir-Whorf Hypothesis - “The claim that the language we speak determines the thoughts we are capable of having. Its weakest form, that we often think in words, is obvious; its strongest form, that we are incapable of thoughts that our language lacks words or constructions for, is clearly false.” (21cC 2014)

• scope - “The portion of the code base over which a variable is declared and accessible. Good coding style depends on keeping the scope of variables small.” (21cC 2014)

• segfault - “Segmentation fault.” (21cC 2014)

• segmentation fault - “Touching an incorrect segment of memory. Causes the operating system to halt the program immediately, and so often used metonymically to refer to any program-halting error.” (21cC 2014)

• SHA - “Secure Hash Algorithm.” (21cC 2014)

• shell - “A program that allows users to interact with an operating system, either at a command line or via scripts.” (21cC 2014)

• SQL - “Structured Query Language. A standardized means of interacting with databases.” (21cC 2014)

• stack - “The space in memory where function execution occurs. Notably, automatic variables are placed here. Each function gets a frame, and every time a subfunction is called, its frame is conceptually stacked on top of the calling function's frame.” (21cC 2014)

• static allocation - “The method by which variables with file scope and variables inside functions declared as static are allocated. Allocation occurs before the program starts, and the variable continues to exist until the end of the program.” (21cC 2014)

• test harness - “A system for running a sequence of unit tests and integration tests. Provides easy setup and teardown of auxiliary structures, and allows for checking of failures that may (correctly) halt the main program.” (21cC 2014)

• thread - “A sequence of instructions that a computer executes independently of any other thread.” (21cC 2014)

• token - “A set of characters to be treated as a semantic unit, such as a variable name, a keyword, or an operator like * or +. The first step in parsing text is to break it down into tokens; strtok_r and strtok_n are designed for this.” (21cC 2014)

• type punning - “Casting a variable of one type to a second type, thus forcing the compiler to treat the variable as data of the second type. For example, given struct {int a; char *b:} astruct, then (int) astruct is an integer (but for a safer alternative, see “C, with fewer seams”). Frequently not portable; always bad form.” (21cC 2014)

• type qualifier - “A descriptor of how the compiler may handle a variable. Is unrelated to the type of the variable (int, float, et cetera). C's only type qualifiers are const, restrict, volatile, and _Atomic.” (21cC 2014)

• union - “A single block of memory that can be interpreted as one of several types.” (21cC 2014)

• unit test - “A block of code to test a small piece of a code base. Compare with integration test.” (21cC 2014)

• UI - “User interface. For a C library, this includes the typedefs, macro definitions, and function declarations that users are expected to be comfortable with when using the library.” (21cC 2014)

• UTF - “Unicode Transformation Format.” (21cC 2014)

• variadic function - “A function that takes in a variable number of inputs (e.g., printf).” (21cC 2014)

• wide-character encoding - “An encoding of text where each human-language character is given a fixed number of chars. For example, UTF-32 guarantees that each Unicode character is expressed in exactly 4 bytes. Contrast this definition with multibyte encoding.” (21cC 2014)

• XML - “Extensible Markup Language.” (21cC 2014)

Fair Use Sources:

• 21st Century C on DuckDuckGo
• B00NYBRH30 (21cC 2014)
• 21st Century C for Archive Access for Fair Use Preservation, quoting, para[[phrasing, excerpting and/or commenting upon