Joerg-Cyril Hoehle <hoehle-sorry@tzd.dont.telekom.spam.de.me> wrote:
+---------------
| One solution has been to have READ return what I call an annotated
| structure containing for each object within the structure
| supplementary information about the file position, line number and
| partial structural contents (like CMUCL prints nicely). These
| annotations would be invisible to the normal processing, macroexpansion etc.
+---------------
Shriram Krishnamurthi's "McMicMac" Parser and "Zodiac" source-correlating
macro-expander (included as part of the MrSpidey debugger component of
DrScheme) do *exactly* this, IIRC. See:
http://www.cs.rice.edu/CS/PLT/packages/doc/m3/index.htm
specifically:
http://www.cs.rice.edu/CS/PLT/packages/doc/m3/node4.htm
http://www.cs.rice.edu/CS/PLT/packages/doc/m3/node7.htm
+---------------
| So, how do compilers refer to specific source file locations except
| for the obvious pipelined processing which allows to peek the current
| input streams file position -- which now sounds like a hack?
+---------------
See above...
-Rob
-----
Rob Warnock, 8L-855 rpw3@sgi.com
Applied Networking http://reality.sgi.com/rpw3/
Silicon Graphics, Inc. Phone: 650-933-1673
1600 Amphitheatre Pkwy. FAX: 650-933-0511
Mountain View, CA 94043 PP-ASEL-IA