(missing)
Re: [Scheme-reports] library at file level (was: Ratification vote for R7RS Small) John Cowan (13 May 2013 14:48 UTC)
Re: [Scheme-reports] library at file level Per Bothner (13 May 2013 16:54 UTC)
Re: [Scheme-reports] library at file level Andy Wingo (15 May 2013 19:05 UTC)
Re: [Scheme-reports] library at file level John Cowan (15 May 2013 19:14 UTC)
Re: [Scheme-reports] library at file level taylanbayirli@gmail.com (15 May 2013 20:12 UTC)
Re: [Scheme-reports] library at file level John Cowan (15 May 2013 21:07 UTC)

Re: [Scheme-reports] library at file level (was: Ratification vote for R7RS Small) John Cowan 13 May 2013 14:47 UTC

Sam Tobin-Hochstadt scripsit:

> Yes, this can work, but only because the procedures and macros could
> be reorganized not to be in mutually recursive libraries. This isn't
> solving the actual hard (that is to say, impossible) problem, which is
> when bmac is defined using aproc, and aproc is defined using bmac.

Indeed not, as my final paragraph noted.  But that has nothing to do
with libraries, either.  The libraries just provide a static type system
that prevents such problematic cases from occurring beyond the compiler's
event horizon.  A compiler that can see the whole program if it wants to,
like javac, needs no such helps.

--
The experiences of the past show                John Cowan
that there has always been a discrepancy        cowan@ccil.org
between plans and performance.                  http://www.ccil.org/~cowan
        --Emperor Hirohito, August 1945

_______________________________________________
Scheme-reports mailing list
Scheme-reports@scheme-reports.org
http://lists.scheme-reports.org/cgi-bin/mailman/listinfo/scheme-reports