3 ms·

If referring to TinyScheme being used for sandboxing, that still uses garbage collection. https://github.com/sungit/TinyScheme/blob/master/tinyscheme-1.40/sche

• astrange 3y ago
  GCC also uses garbage collection during the compilation process, but that doesn't make it happen at runtime or C a Scheme.
  • hayley-patton 3y ago
    Okay, cool, but the collector is used at runtime with TinyScheme. _cons calls get_cell calls get_cell_x calls _get_cell calls gc for example; what makes you think otherwise?
    • astrange 3y ago
      The system I'm talking about uses TinyScheme as a code generation system, but doesn't use it as an interpreter in-kernel afaik.
      • hayley-patton 3y ago
        Right. I found <https://www.ise.io/wp-content/uploads/2017/07/apple-sandbox.pdf https://www.ise.io/wp-content/uploads/2017/07/apple-sandbox....> which agrees with you (on page 9). Guess it's down to defining "at runtime" now; the TinyScheme code (and GC) and Scheme code for the sandbox definitions are shipped to a user of macOS, and the user can invoke sandbox-exec with new sandboxing definitions (e.g. <https://jmmv.dev/2019/11/macos-sandbox-exec.html https://jmmv.dev/2019/11/macos-sandbox-exec.html>), running TinyScheme and Scheme code. So I'd think Scheme is part of the entire sandbox system, even if not in the kernel?
      • lispm 3y ago
        Sounds like it is not surprising that it does not use a GC at runtime, given that it does not use Scheme at runtime.