-
Notifications
You must be signed in to change notification settings - Fork 0
/
terms.txt
55 lines (55 loc) · 3.51 KB
/
terms.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
// - a comment
function - a set of statements, made up of four parts: a return type, a name, parameter list and the function body
output - something that is showed to you via the program, usually an output of text
compiler - something that turns your source code into object/machine code
error - bad stuff, usually something is wrong, many types in C++: run time, compile-time, link-time(?)
linker - something that takes object/machine codes (can take multiple files of it), links it together and creates an executable
command line - terminal, thing to compile in if you're not using an IDE (like me)
executable - the final output from the compile and linker, which will run your code
object code - code that your computer hardware can interpret
comment - something to annotate your code and explain stuff
import - import statement to gain use of things, i.e. `import std` means import the standard library
library - a collection of programs which give access to additional features, think I/O in our first program
module - one piece of the library, so like the iostream from the std library
bug - a problem, named that because an actual moth got in a computer back in the day
main() - a function that is needed in C++ files, although i have seen some exist without one
C++ - language that i be learning, was originally called C with Classes
IDE - lol, just don't... no i jest, it just helps out with writing C++ so you can highlight syntax and see errors, then compile and run within 1 window
source code - the stuff you write, which you understand, in syntax of the language you're writing in usually with intentions to be compiled eventually
statement - a sentence in programming really, see the hello world lines in my 1st program
#include - apparently the old way to using import, but i still see it used today
debugging - to get rid of the bugs, to comb through your code and see where things went wrong
<< - the output operator
header file - <iostream> in my case, which is from the standard library but they be local too. you just import when you need things from them
program - the whole thing, source code and that
compile-time - the time when it's compiling
cout - see out, character output stream
std - standard library
assignment - when you give a value to a variable
increment - adding 1, usually done in loops
type - there are 5, but it's what your data represents, i.e. a number, a string
declaration - statement that gives a name and type to an object
object - some mory that holds a value of given type
int - number
== - equals to
< - less than
double - floating point number
!= - not equals to
<= - less than or equal to
= - assignment
> - greater than
++ - increment
>= - greater than or equal to
string - a list of characters, used to form sentences in programs
auto - used when the type is obvious and some complex cases
definition - a declaration which sets aside memory for an object
operator - think arithmetic, think of + represents addition, > represents greater than
concatenation - adds two strings together, so "Hello" + "World" is "HelloWorld"
name - usually what you give a variable, an identifier
value - a set of bits in memory interpreted according to a type
widening - conversions that preser information, such as char to int
cin - see in, character input stream, takes what a user types in
initialization - giving a value to your variables, always do it
type safety - see the above about initialization, it ensures all objects are used according to their rules of their type
decrement - minus 1, opposite of increment
truncation - rounds down, towards zero