[Chicken-users] schemish/chickenish way to make configurable executables?

I'm curious to hear opinions on conditional complication and configuration using Chicken scheme. Say for example I want to enable or disable the use of a particular library or feature and I want there to be no trace of it in the executable. I can use a preprocessor such as cpp but I imagine

Re: [Chicken-users] schemish/chickenish way to make configurable executables?

On Sat, Nov 02, 2013 at 11:35:22PM -0700, Matt Welland wrote: I'm curious to hear opinions on conditional complication and configuration using Chicken scheme. Say for example I want to enable or disable the use of a particular library or feature and I want there to be no trace of it in the

Re: [Chicken-users] schemish/chickenish way to make configurable executables?

Hi Peter, It looks like cond-expand does enough to achieve what I want. Thanks! Matt -=- On Sun, Nov 3, 2013 at 2:58 AM, Peter Bex peter@xs4all.nl wrote: On Sat, Nov 02, 2013 at 11:35:22PM -0700, Matt Welland wrote: I'm curious to hear opinions on conditional complication and

Re: [Chicken-users] schemish/chickenish way to make configurable executables?

There is also the feature-test egg which is useful in combination with the FFI. Jim On Nov 3, 2013, at 9:56, Matt Welland estifo...@gmail.com wrote: Hi Peter, It looks like cond-expand does enough to achieve what I want. Thanks! Matt -=- On Sun, Nov 3, 2013 at 2:58 AM, Peter Bex