Examples of org.dynalang.dynalink.DynamicLinker

• org.dynalang.dynalink.DynamicLinker
  The linker for {@link RelinkableCallSite} objects. Users of it (scripting frameworks and language runtimes) have tocreate a linker using the {@link DynamicLinkerFactory} and invoke its link method from the invokedynamic bootstrapmethods to set the target of all the call sites in the code they generate. Usual usage would be to create one class per language runtime to contain one linker instance as:

   class MyLanguageRuntime { private static final GuardingDynamicLinker myLanguageLinker = new MyLanguageLinker(); private static final DynamicLinker dynamicLinker = createDynamicLinker(); private static DynamicLinker createDynamicLinker() { final DynamicLinkerFactory factory = new DynamicLinkerFactory(); factory.setPrioritizedLinker(myLanguageLinker); return factory.createLinker(); } public static CallSite bootstrap(MethodHandles.Lookup caller, String name, MethodType type) { return dynamicLinker.link(new MonomorphicCallSite(CallSiteDescriptorFactory.create(lookup, name, type))); } } 

  Note how there are three components you will need to provide here:

  • You're expected to provide a {@link GuardingDynamicLinker} for your own language. If your runtime doesn'thave its own language and/or object model (i.e. it's a generic scripting shell), you don't need to implement a dynamic linker; you would simply not invoke the {@code setPrioritizedLinker} method on the factory, or even better,simply use {@link DefaultBootstrapper}.
  • The performance of the programs can depend on your choice of the class to represent call sites. The above example used {@link MonomorphicCallSite}, but you might want to use {@link ChainedCallSite} instead. You'll need toexperiment and decide what fits your language runtime the best. You can subclass either of these or roll your own if you need to.
  • You also need to provide {@link CallSiteDescriptor}s to your call sites. They are immutable objects that contain all the information about the call site: the class performing the lookups, the name of the method being invoked, and the method signature. The library has a default {@link CallSiteDescriptorFactory} for descriptors that you can use,or you can create your own descriptor classes, especially if you need to add further information (values passed in additional parameters to the bootstrap method) to them.

  @author Attila Szegedi

Related Classes of org.dynalang.dynalink.DynamicLinker