Alex Shinn scripsit:> > BTW, if the above macro is defined in a library, which file wouldThat's explicitly undefined: the implementation applies an
> > be included? The file in the same location of the library or macro
> > caller location?
> By the time the include is expanded it has no idea in which file it
> was originally defined (barring some sort of self-introspection on
> source info), so the include path would naturally be relative to the
> caller location.
implementation-specific algorithm to cast the string to a file name.
_______________________________________________ Scheme-reports mailing list Scheme-reports@x http://lists.scheme-reports.org/cgi-bin/mailman/listinfo/scheme-reports