Syntax and Semantic Errors
Since I am only on page 384, this will be a short(ish) post, but I wanted to put this idea out there and see if it connected with anyone else. In my non-school life, I work for a software company and spend a lot of time programming, so I glance over the Anwar stuff with an eye for bugs, but not too critically (I am trying to get through the book after all). But I did catch a syntax error in the code presented on page 89:
// int main()
// std::cout << ‘My thoughts unaloud look like this!\n’
This is c++ code and the “//”s mean that what follows on the line is a comment (until the next carriage return, which is why I included the output as one line), but the return line is not commented out. If you were to try to run this through a compiler, you would get a syntax error. When I first saw this, I didn’t think it was intentional, but I didn’t have enough of the book read to feel like I could associate it with something. But while flipping through the book today after having read about the bug in the scene loading code on page 382 something clicked. “Bugs” in code are semantic errors, problems in meaning, where the error above is a syntax error, an error in the grammar of the language (grammar in the linguistic sense, the rules of language; possible sentences versus impossible sentences). You know who makes a lot of semantic errors in their speech? Xanther. But jingjing’s narrations make a lot of syntax errors, which makes the sections harder to read, your brain can’t compile correctly, and you have to debug the sentences.
I got to thinking, couldn’t the syntax and semantic errors run through all different layers of the book? That seems to me to be sort of the idea of the signiconic. It’s sort of a syntax error in the language of books, so we have to stop and debug it, figure it out.
It could also be that I am just very sleep deprived.