On Mon, Jul 2, 2012 at 9:58 AM, Alan Watson <[email protected]> wrote:
>> It is very important to have a clean separation between
>> library declarations and Scheme code
>
> OK, but it is also very important to have a clean separation between a 
> library interface and a library implementation. I think the current library 
> system is indeed broken in this sense and does needs fixing, somehow. I'd be 
> very happy with include-library-declaration.
>
> I don't quite see how export-interface fixes this problem. I'm thinking, for 
> example, of a library that uses cond-expand to include files containing 
> implementation-dependent code and, for clarity, wants to put all of the 
> implementation-dependent imports in the same files as the 
> implementation-dependent code.

This can be achieved trivially by cond-expanding imports of
implementation-specific utility libraries.

-- 
Alex

_______________________________________________
Scheme-reports mailing list
[email protected]
http://lists.scheme-reports.org/cgi-bin/mailman/listinfo/scheme-reports

Reply via email to