TDF Diagnostic Specification, Issue 3.0

January 1998

3.0.1 - ~exp_to_source
3.0.2 - ~diag_id_source
3.0.3 - ~diag_type_scope
3.0.4 - ~diag_tag_scope

3. Reserved diagnostic TOKENs

Reserved TOKENs were used for diagnostic extensions to EXPs, to avoid adding new constructs the contents of an existing UNIT. All other parts of the diagnostic system occur in other UNITs.

3.0.1. ~exp_to_source

	body:		EXP sh
	from:		SOURCEMARK
	to:		SOURCEMARK
		   -> EXP sh

Records that the EXP body arose from translating program between SOURCEMARK from and SOURCEMARK to (inclusive).

3.0.2. ~diag_id_source

	body:		EXP sh
	name:		TDFSTRING(k, n)
	access:		EXP POINTER(al)
	type:		DIAG_TYPE
		   -> EXP sh

Within the EXP body a variable named name of DIAG_TYPE type can be accessed via the EXP access.

3.0.3. ~diag_type_scope

	body:		EXP sh
	name:		TDFSTRING(k, n)
	type:		DIAG_TYPE
		   -> EXP sh

Within the EXP body a source language type named name of DIAG_TYPE type is valid.

3.0.4. ~diag_tag_scope

	body:		EXP sh
	name:		TDFSTRING(k, n)
	type:		DIAG_TYPE
		   -> EXP sh

This TOKEN is obsolete.