379: Forgetting - Revision history

CalibansCreations: /* Explanation */

2025-04-03T07:48:05Z

‎Explanation

ConscriptGlossary: Cross-reference

2024-11-23T08:04:57Z

Cross-reference

162.158.158.196 at 23:19, 22 November 2024

2024-11-22T23:19:09Z

CalibansCreations: /* Explanation */

2024-11-07T12:43:09Z

‎Explanation

172.70.34.202: add lowercase text category

2023-05-12T16:20:39Z

add lowercase text category

Theusaf: Reverted edits by Donald Trump (talk) to last revision by CRLF

2022-05-26T19:57:54Z

Reverted edits by Donald Trump (talk) to last revision by CRLF

Show changes

Donald Trump: Reverted edit by anti-crap user

2022-05-26T19:04:27Z

Reverted edit by anti-crap user

Show changes

CRLF: Reverted vandalism with User:CRLF/OneClickUndo.js

2022-05-26T17:51:24Z

Reverted vandalism with User:CRLF/OneClickUndo.js

Show changes

Donald Trump: Reverted edit by anti-crap user

2022-05-26T17:24:14Z

Reverted edit by anti-crap user

Show changes

CRLF: Reverted vandalism with User:CRLF/OneClickUndo.js

2022-05-23T18:44:17Z

Reverted vandalism with User:CRLF/OneClickUndo.js

Show changes

@@ Line 10: / Line 10: @@
 [[Cueball]] is writing a piece of code (probably in the programming language {{w|C++}}) that removes an item from a data structure called a {{w|Linked list}} (the first two lines of the text). Then, he writes a {{w|Comment (computer programming)|comment}} (delimited by the [[Commented|double slashes]]) relating the code to his personal life. Finally, he adds an {{w|Assertion (computing)|assertion}}, which is normally a formal specification of a condition that should always be true (with which the programmer ensures that, e.g. mass is not negative). But in this case, instead of asserting a software-related predicate, he asserts that "it's going to be okay" - and because of how {{w|String literal|string literals}} are treated by the compiler, the assertion will be true.
-An "assert" is a programming statement that allows you to insert sanity checks into your code. For example, if you were writing a program to calculate the speed of a neutrino, then at the end of the calculation you could say:
+An "assert" (aside from "[[1339: When You Assume|mak[ing] an ass out of the emergency response team]]") is a programming statement that allows you to insert sanity checks into your code. For example, if you were writing a program to calculate the speed of a neutrino, then at the end of the calculation you could say:
 :<code>assert ( velocity_of_neutrino <= speed_of_light );</code>

@@ Line 8: / Line 8: @@
 ==Explanation==
-[[Cueball]] is writing a piece of code (probably in the programming language {{w|C++}}) that removes an item from a data structure called a {{w|Linked list}} (the first two lines of the text). Then, he writes a {{w|Comment (computer programming)|comment}} (delimited by the double slashes) relating the code to his personal life. Finally, he adds an {{w|Assertion (computing)|assertion}}, which is normally a formal specification of a condition that should always be true (with which the programmer ensures that, e.g. mass is not negative). But in this case, instead of asserting a software-related predicate, he asserts that "it's going to be okay" - and because of how {{w|String literal|string literals}} are treated by the compiler, the assertion will be true.
+[[Cueball]] is writing a piece of code (probably in the programming language {{w|C++}}) that removes an item from a data structure called a {{w|Linked list}} (the first two lines of the text). Then, he writes a {{w|Comment (computer programming)|comment}} (delimited by the [[Commented|double slashes]]) relating the code to his personal life. Finally, he adds an {{w|Assertion (computing)|assertion}}, which is normally a formal specification of a condition that should always be true (with which the programmer ensures that, e.g. mass is not negative). But in this case, instead of asserting a software-related predicate, he asserts that "it's going to be okay" - and because of how {{w|String literal|string literals}} are treated by the compiler, the assertion will be true.
 An "assert" is a programming statement that allows you to insert sanity checks into your code. For example, if you were writing a program to calculate the speed of a neutrino, then at the end of the calculation you could say:

@@ Line 8: / Line 8: @@
 ==Explanation==
-[[Cueball]] is writing a piece of code (probably in the programming language {{w|C++}}) that removes an item from a data structure called a {{w|Linked list}} (the first two lines of the text). Then, he writes a {{w|Comment (computer programming)|comment}} (delimited by the double slashes) relating the code to his personal life. Finally, he adds an {{w|Assertion (computing)|assertion}}, which is normally a formal specification of a condition that should always be true (with which the programmer ensures that, e.g. mass is not negative). But in this case, instead of asserting a software-related predicate, he asserts that "it's going to be okay" - and because of how {{w|String literal|string literals}} are treated by the interpreter, the assertion will be true.
+[[Cueball]] is writing a piece of code (probably in the programming language {{w|C++}}) that removes an item from a data structure called a {{w|Linked list}} (the first two lines of the text). Then, he writes a {{w|Comment (computer programming)|comment}} (delimited by the double slashes) relating the code to his personal life. Finally, he adds an {{w|Assertion (computing)|assertion}}, which is normally a formal specification of a condition that should always be true (with which the programmer ensures that, e.g. mass is not negative). But in this case, instead of asserting a software-related predicate, he asserts that "it's going to be okay" - and because of how {{w|String literal|string literals}} are treated by the compiler, the assertion will be true.
 An "assert" is a programming statement that allows you to insert sanity checks into your code. For example, if you were writing a program to calculate the speed of a neutrino, then at the end of the calculation you could say:

@@ Line 13: / Line 13: @@
 :<code>assert ( velocity_of_neutrino <= speed_of_light );</code>
-If the assertion fails, then the program will stop with an error. This would be much better than publishing an embarrassing paper, for example.
+If the assertion fails, then the program will stop with an error. This would be much better than [[955|publishing an embarrassing paper]], for example.
 Cueball realizes that he cannot forget his emotional event through the use of two commands as he can with a computer, which only makes him feel sad about an unsaid event, the item -- in a sense -- that cannot be removed.  He writes two comments further clarifying his sense of hopelessness over this event, followed by an assertion that "it will be okay," something that has nothing to do with the code he is writing.

← Older revision		Revision as of 16:20, 12 May 2023
Line 37:		Line 37:
	[[Category:Comics featuring Cueball]]		[[Category:Comics featuring Cueball]]
	[[Category:Programming]]		[[Category:Programming]]
		+	[[Category:Comics with lowercase text]]