This is a question that I’ve always wanted to know the answer, but never really asked.
How does code written by one language, particularly an interpreted language, get called by code written by a compiled language.
For example, say I’m writing a game in C++ and I outsource some of the AI behavior to be written in Scheme. How does the code written in Scheme get to a point that is usable by the compiled C++ code? How is it used by the C++ source code, and how is it used by the C++ compiled code? Is there a difference in the way it’s used?
There is no single answer to the question that works everywhere. In general, the answer is that the two languages must agree on “something” — a set or rules or a “calling protocol”.
In a high level, any protocol needs to specify three things:
The details depend heavily on the protocol itself.
Sometimes the two languages conspire to work together. Sometimes the two languages agree to support some outside-defined protocol. These days, the OS or the “runtime environment” (.NET and Java) is often involved as well. Sometimes the ability only goes one way (“A” can call “B”, but “B” cannot call “A”).
Notice that this is the same problem that any language faces when communicating with the OS. The Linux kernel is not written in Scheme, you know!
Let’s see some typical answers from the world of Windows:
C with C++: C++ uses a contorted (“mangled”) variation of the “C protocol”. C++ can call into C, and C can call into C++ (although the names can be quite messy sometimes and it might need external help translating the names). This is not just Windows; it’s generally true in all platforms that support both. Most popular OS’s use a “C protocol” as well.
VB6 vs. most languages: VB6’s preferred method is the “COM protocol”. Other languages must be able to write COM objects to be usable from VB6. VB6 can produce COM objects too (although not every possible variation of COM objects).
VB6 can also talk a very limited variation of the “C protocol”, and then only to make calls outside: it cannot create objects that can be talked to directly via the “C protocol”.
.NET languages: All .NET languages communicate compile to the same low-level language (IL). The runtime manages the communication and from that point of view, they all look like the same language.
VBScript vs. other languages: VBScript can only talk a subset of the COM protocol.
One more note: SOAP “Web Services” is really a “calling protocol” as well, like many other web-based protocol that are becoming popular. After all, it’s all about talking to code written in a different language (and running in a different box at that!)