Home | About | Partners | Contact Us

SourceForge Logo

Quick Links
Home
News
Status
Building XL
XL Mailing List

Understanding XL
Conceptual overview
XL examples
Inside XL
Concept Programming

In depth
Browse GIT
Bugs
SourceForge Info
Contact

Other projects
GNU Project
The Mozart Project

XLR: Extensible Language and Runtime

The art of turning ideas into code

XL Object Model

Prev: The XL runtime library

Up

Next: XL operators

While XL is object oriented, it doesn't have closed classes as in C++ or C# or Java. The shape objects example should illustrate why.

The idea is to, finally, offer true encapsulation. There is no way by looking at the interface to deduce how it is actually implemented. It doesn't mean that the compiler doesn't see it (so if you create a ".o" file for the module implementation, it needs to contain supplemental information that would go in a .h file in C++). The model also features multi-way dynamic dispatch as in the Intersect function in the example.

Please note that I do consider having also a fairly standard class notation, but this will be just a simple plug-in generating the kind of code below (and adding things like using X to simulate the implicit reference to this in C++).

Prev: The XL runtime library

Up

Next: XL operators


Copyright 2008 Christophe de Dinechin (Blog)
E-mail: XL Mailing List (polluted by spam, unfortunately)