Abstract | ||
---|---|---|
Scripting languages are used in conjuction with C code in two ways: as extension languages, where the interpreter is embedded as a library into an application; or as extensible languages, where the interpreter loads C code as add-on modules. These two scenarios share many similarities, as in both of them two-way communication of code and data needs to take place. However, the differences between them impose design tradeoffs that affect the C API that bridges the two languages, often making a scripting language more suitable for extending than embedding, or vice-versa. This paper discusses how these tradeoffs are handled in the APIs of popular scripting languages, and the impact on their use as embedded or extensible languages. |
Year | Venue | Keywords |
---|---|---|
2007 | JOURNAL OF UNIVERSAL COMPUTER SCIENCE | programming languages,application programming interfaces |
Field | DocType | Volume |
Domain-specific language,Query language,Second-generation programming language,Programming language,Comparison of multi-paradigm programming languages,Computer science,Read–eval–print loop,Third-generation programming language,Scripting language,Ontology language | Journal | 13 |
Issue | ISSN | Citations |
6 | 0948-695X | 5 |
PageRank | References | Authors |
0.77 | 5 | 2 |
Name | Order | Citations | PageRank |
---|---|---|---|
Hisham Muhammad | 1 | 6 | 1.82 |
Roberto Ierusalimschy | 2 | 463 | 54.25 |