Ah great, thanks for the explanation. That doesn't seem like a show stopper for what I'm trying to do. :-)
Much appreciated! iain On Sun, Dec 22, 2019 at 10:47 PM John Cowan <[email protected]> wrote: > Procedures and code files that contain both Scheme and C must be compiled, > but the resulting compiled code can be loaded into the environment and > invoked from the interpreter. Obviously pure C files must be compiled by a > C compiler. > > On Mon, Dec 23, 2019 at 12:20 AM Iain Duncan <[email protected]> > wrote: > >> >> >> (trimmed) >> >>> >>> >>>> I'm hoping to be able to achieve some sort of hot coding, where >>>> functions and definitions in my scheme environment may get overwritten by >>>> the user doing live coding. >>>> >>> >>> That's practical. Eval maintains a global environment which can be >>> changed by evaluating new definitions. >>> >>> Are there limitations on what kind of thing can be dynamically evaluated >>>> or can I evaluate anything, but with perhaps a performance penalty? >>>> >>> >>> You can evaluate anything that doesn't need access to the foreign >>> function interface. >>> >> >> Thank you for the explanations. For the above, I'm not sure I quite >> understand. Does this mean that if I have real-time scheme code sent to the >> plugin, and it will be run by eval, that this code can not calls functions >> that are defined in C and made available to scheme? Can it call functions I >> have precompiled that call into C? Or if I'm misunderstanding, do you mind >> expanding on what the last statement means for a newbie? >> >> thanks >> Iain >> >> >
