Editing 371: Compiler Complaint
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 8: | Line 8: | ||
==Explanation== | ==Explanation== | ||
β | A {{w|Compiler|compiler}} is a program that converts code into machine instructions that a computer can run. A {{w|Pointer (computer programming)| | + | A {{w|Compiler|compiler}} is a program that converts code into machine instructions that a computer can run. A {{w|Pointer (computer programming)|Pointer}} is a {{w|Variable (computer science)|variable}} within a computer program that is used to reference a memory location. A {{w|Segmentation Fault|Segmentation Fault (segfault)}} is an error that occurs when a program attempts to access an invalid section of memory. Segfaults usually cause a program to crash in an ungraceful fashion and fixing them can be difficult. |
In the comic, the computer starts talking to [[Cueball]] and compares a segfault with the unpleasant feeling one gets when they experience a {{w|hypnic jerk}}. The computer then tells the programmer to "double-check your damn pointers," as segfaults usually arise from a program attempting to access memory that is referenced by an invalid pointer. | In the comic, the computer starts talking to [[Cueball]] and compares a segfault with the unpleasant feeling one gets when they experience a {{w|hypnic jerk}}. The computer then tells the programmer to "double-check your damn pointers," as segfaults usually arise from a program attempting to access memory that is referenced by an invalid pointer. | ||
β | |||
β | |||
The title-text references GNU-style {{w|autoconf}} configuration scripts. These scripts check certain features of the system they're running on in order to build a program correctly; for example, certain systems expect system calls to occur in a specific way, and the autoconf script will detect this and alter the program to match the expectation. Invariably (and memetically), these scripts include a check to determine "whether the build environment is sane." This actually checks whether the path to the current folder has "unsafe" characters, and whether a newly created file is older than the script itself, which could indicate a very esoteric filesystem, a corrupted source archive, or just a system clock that's set incorrectly; however, since these file modification dates are an important part of how the autoconf script does its work, it can't go any further in an "insane" environment. In any case, the joke is that an insane build environment is nothing like an insane person, yet Randall is equating the two. | The title-text references GNU-style {{w|autoconf}} configuration scripts. These scripts check certain features of the system they're running on in order to build a program correctly; for example, certain systems expect system calls to occur in a specific way, and the autoconf script will detect this and alter the program to match the expectation. Invariably (and memetically), these scripts include a check to determine "whether the build environment is sane." This actually checks whether the path to the current folder has "unsafe" characters, and whether a newly created file is older than the script itself, which could indicate a very esoteric filesystem, a corrupted source archive, or just a system clock that's set incorrectly; however, since these file modification dates are an important part of how the autoconf script does its work, it can't go any further in an "insane" environment. In any case, the joke is that an insane build environment is nothing like an insane person, yet Randall is equating the two. |