Editing Talk:371: Compiler Complaint
Please sign your posts with ~~~~ |
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 51: | Line 51: | ||
I do not think Randall is suggesting that segfaults are a compiler issue. The insane computer stopped the person before compiling, because this would be the only time that he could change the code to prevent possible segfaults during runtime.{{unsigned|Flewk}} | I do not think Randall is suggesting that segfaults are a compiler issue. The insane computer stopped the person before compiling, because this would be the only time that he could change the code to prevent possible segfaults during runtime.{{unsigned|Flewk}} | ||
:You're totally right; unless it's an interpreter, or the compiler is running some code at compile-time, the compiler will almost never get a segfault itself due to a buggy program. I updated the explanation to clarify this. [[User:APerson|APerson]] ([[User talk:APerson|talk!]]) 06:17, 29 October 2018 (UTC) | :You're totally right; unless it's an interpreter, or the compiler is running some code at compile-time, the compiler will almost never get a segfault itself due to a buggy program. I updated the explanation to clarify this. [[User:APerson|APerson]] ([[User talk:APerson|talk!]]) 06:17, 29 October 2018 (UTC) | ||
β | |||
β | |||
β |