Bigloo.NET: compiling Scheme to .NET CLR.

Abstract

This paper presents the compilation of the Scheme programming language to .NET. This platform provides a virtual machine, the Common Language Runtime (CLR), that executes bytecode, the Common Intermediate Language (CIL). Since CIL was designed with language agnosticism in mind, it provides a rich set of language constructs and functionalities. As such, the CLR is the first execution environment that offers type safety, managed memory, tail recursion support and several flavors of pointers to functions. Therefore, the CLR presents an interesting ground for functional language implementations. We discuss how to map Scheme constructs to CIL. We present performance analyses on a large set of real-life and standard Scheme benchmarks. In particular, we compare the speed of these programs when compiled to C, JVM and .NET. We show that in term of speed performance of the Mono implementation of .NET, the best implementing running on both Windows and Linux, still lags behind C and fast JVMs such as the Sun's implementations.

Метод компіляції типів об’єднання мови TypeScript у проміжну мову CIL платформи .NET

“…На сьогоднішній день існує досить незначна кількість статей, що описують способи трансляції різних мов програмування у проміжну мову CIL платформи .NET чи інші мови байт-кодового типу. Серед таких статей можна виділити опис методів трансляції байт-коду віртуальної машини Java [1] від корейських дослідників та трансляції мови програмування Scheme [2] від французьких вчених. Ці дослідження було розглянуто і проаналізовано у попередніх статтях [3,4,5], які присвячені компіляції Науковий журнал "Комп'ютерно-інтегровані технології: освіта, наука, виробництво" Луцьк, 2023.…”

Event-Based Programming Without Inversion of Control

“…Virtual machines such as the JVM provide no means for explicit stack management, mainly because of security reasons. Thus, languages implementing rst-class continuations have to simulate the run-time stack on the heap which poses serious performance problems [7]. Moreover, programming tools such as debuggers and pro lers rely on run-time information on the native VM stack which they are unable to nd if the stack that programs are using is allocated on the heap.…”

Continuations from generalized stack inspection

“…Mirroring traditional programming languages, these machines do not provide instructions for installing and saving the run-time stack. Usually, Scheme-on-VM implementors give up on first-class continuations [1,2], or they allocate the control stack in the heap of the machine [23]. As Bres, et al [2, section 2] point out, however, with this second strategy, "it might be expected that .…”