On Nov 26, 2008, at 12:44 AM, marcomaggi wrote:
* select target directories;
* enable/disable installation of components (documentation
in different formats, fasl files);
* verify the availability of other libraries;
* inspect the value of constants in C language header files
and detect the size of data structures in foreign libraries;
* preprocess .sls files to make available the above values
at the Scheme level;
It's not a good idea to "preprocess" scheme code. There's only one
processor in Scheme and that's called the macro system. Anything
short of that is plain broken.
If you want to provide configurations, then you should:
(1) generate a library that the user can import,
(2) generate a configuration file with definitions that the user
can include
(3) provide some procedures that figure this at run time, or
(4) provide a set of macros that do this at library compile time.
Aziz,,,
