a specific point in the code. Examples are files that need to be included multiple times or platform-specific implementation details that are essentially part of other self-contained headers. Such files #define PRIoS __PRIS_PREFIX "o" Type DO NOT use DO use Notes void * (or any pointer) %lx %p int64_t %qd, %lld %" PRId64 " 38 Type DO NOT use DO use Notes uint64_t %qu, %llu, %llx %" PRIu64 ", %" PRIx64

avoids giving advice that isn’t clearly enforceable (whether by human or tool). 1.1 Terminology notes In this document, unless otherwise clarified: 1. The term class is used inclusively to mean an “ordinary” comments”, instead using the common term “Javadoc.” Other “terminology notes” will appear occasionally throughout the document. 1.2 Guide notes Example code in this document is non-normative. That is, while

accomplishes the paper’s goals  #1 Skimming (see above)  #2 Read the whole paper sequentially, add notes/annotations  Reviewing  Goal: evaluate potential impact, and limitations  #1 Skimming (see above)