How best to structure lambdanative app code to catch syntax issues at compile time?

[kiatoa]

I'm most familiar with Chicken Scheme where I can put code in modules which ensures syntax issues get caught at compile time. Specifically how best to achieve that with Gambit/lambdanative and more generally how best to structure a complex app? Is there an example of a more complex app that illustrates good practices for lambdanative?

[mgorges]

Structuring code with Modules is described on its Wiki page (like all the other documentation). I don't think it is possible to have any apps that don't include at least the config and ln_core, modules, as the former pulls in the gambit compiler library. Setting up apps with the scripts/lambdanative create <appname> <apptype> process using examples using any of the templates illustrates this.

For a more complex app example look at the health app examples in the LNhealth repository, for example RRate or S5DataLogger.

[kiatoa]

Ah, just what I needed. Thanks. I didn't notice that the tree heading "modules" actually linked to documentation on modules. Oops.