Name Mangling

While Loci was designed without function or method overloading, limited name mangling is still required for some features, and also in general to try to avoid conflicts between normal C function names and Loci generated functions, such as Class methods.

C-like Functions

Here’s an example:

export void function() { }

In this case, the mangling is essentially a no-op, so function() is mangled to function(). This behaviour applies to all non-templated functions in the global namespace in an unnamed export/import (see Modules for more information). These functions are therefore callable to/from C.

Class Method

Here’s an example of a Class method:

class ExampleClass() {
        void method() { }

Mangling will transform this to:


This essentially breaks down into:

Method(type: TypeName([ "ExampleClass" ]), function: FunctionName([ "method" ]))

Namespace Class Method

Here’s a case with a namespace:

namespace Namespace {
        class ExampleClass() {
                void method() { }

The method name now mangles to:


This breaks down into:

Method(type: TypeName([ "Namespace", "ExampleClass" ]), function: FunctionName([ "method" ]))

Named Module Function

Here’s a function inside a Named Module:

export TestModule 1.2.3 {
        void function() { }

This mangles to:


This breaks down into:

Module(name: [ "TestModule" ], version: 1.2.3), FunctionName([ "function" ])