1 21.0.2 3----- 4 5David Paktor: 6The most prominent change is that the Tokenizer's Message 7format has been expanded to show the current Output Position 8and, if applicable, the position relative to the end of the 9most recent PCI Header (to keep in sync with Offset numbers 10displayed by the DeTokenizer.) 11 12The Symbol-Tracing feature has been changed and expanded: 13Its Messages are no longer Advisories, but a class of their 14own called Trace-Notes. When a Traced Symbol is created, the 15Trace-Note Message gives the new Symbol's assigned FCode Token 16(when applicable) in addition to the Data-Type and Scope of 17the definition. 18 19A Trace-Note Message is now also issued when a Traced Symbol 20is invoked. Symbol-Tracing is not fooled by aliases, and a 21failed attempt to create or invoke a Traced Symbol will also 22cause a Trace-Note Message to be displayed. 23 24These expansions are based on some questions asked by one of 25my colleagues while maintaining a very large and convoluted 26body of Legacy code -- questions like: "Where is such-and-so 27definition coming from?" "Which version of it is being used 28here?" "How can I find where exactly that is in the Binary?" 29 30Another change is based on the recent exchange of letters with 31Rolf Schroedter concerning the use of the emit-fcode command. 32In the previous version, arguments to the emit-fcode command 33were limited to the range of user-defined FCodes, i.e., 0x800 34to 0xFFF. The new version permits numbers in the entire range 35of valid FCodes, 0x010 to 0xFFF, which includes the sub-ranges 36that are reserved for Vendor-Specific FCodes. 37 38