
AbstractThis paper presents language interoperability issues appearing in order to implement support for the BETA language in the Java-based Eclipse integrated development environment. One of the challenges is to implement plug-ins in BETA and be able to load them in Eclipse. In order to do this, some form of language interoperability between Java and BETA is required. The first approach is to use the Java Native Interface and use C to bridge between Java and BETA. This results in a workable, but complicated solution. The second approach is to let the BETA compiler generate Java class files. With this approach it is possible to implement plug-ins in BETA and even inherit from Java classes. In the paper the two approaches are described together with part of the mapping from BETA to Java class files.
.NET, debugger, CLR, Language interoperability, BETA, JVM, Eclipse, Java, Theoretical Computer Science, Computer Science(all)
.NET, debugger, CLR, Language interoperability, BETA, JVM, Eclipse, Java, Theoretical Computer Science, Computer Science(all)
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 0 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Average | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average |
