💾 Archived View for blitter.com › apl-books › APLX50 › APLX-manual › www.microapl.com › apl_help › c… captured on 2023-01-29 at 14:38:04.
⬅️ Previous capture (2022-07-17)
-=-=-=-=-=-=-
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML> <HEAD> <TITLE>Custom interfaces</TITLE> <META NAME="DESCRIPTION" CONTENT="APL language help page: Custom interfaces"> <META NAME="KEYWORDS" CONTENT="Ruby,apl,aplx,apl help"> <!-- %%COMMON_HEAD%% --> <META http-equiv="Content-Type" content="text/html; charset=utf-8"> <LINK rel="stylesheet" type="text/css" href="http://www.microapl.com/styles_apl_help.css"> <!-- %%END%%--> </HEAD> <body> <table> <tr> <td width="800" valign="top" colspan="2"> <center>Topic: <A HREF="ch.htm">APLX Help</A> : <A HREF="ch_070.htm">Interfacing to other languages</A> : <A HREF="ch_070_090.htm">Custom interfaces</A> </center> <center> [<A HREF="ch_070_100.htm">Next</A> | <A HREF="ch_070_060.htm">Previous</A> | <A HREF="ch.htm">Contents</A> | <A HREF="help_index.htm">Index</A> | <A HREF="http://www.microapl.co.uk/apl/index.html">APL Home</A> ]</center> <br></td> </tr> <tr> <td width="120"> <a href="http://www.microapl.co.uk/apl/index.html"><img height="68" border="0" width="119" src="MicroAPL_logo.gif" alt="www.microapl.co.uk"></a> </td> <td align="left" valign="bottom"> <h1>Custom interfaces</h1> </td> </tr> <tr> <td width="800" valign="top" colspan="2"> <hr> <H2>Specifying a call a custom object-oriented interface</H2> <p>If the environment string (left argument) for <A HREF="ch_020_070_505.htm"><code>⎕NEW</code></A>, <A HREF="ch_020_070_345.htm"><code>⎕GETCLASS</code></A>, or <A HREF="ch_020_070_095.htm"><code>⎕CALL</code></A> is not one of the standard options described in previous sections, APLX will attempt to load a shared library to implement the interface. The name of the shared library it tries to load will be <tt>aplxobj_XXX.dll</tt> (under Windows), or <tt>aplxobj_XXX.bundle</tt> (under MacOS), where XXX is the environment string supplied as the left argument.</p> <p>This makes it possible to extend APLX to interface to:</p> <ul><li><p>Other modern object-oriented languages which support <i>reflection</i>, such as Python.</p></li> <li><p>Custom libraries or application interfaces which can be called from a shared library and where an object-oriented interface makes sense. For example, a class library written in C++ could be packaged up is this way.</p></li> </ul> <p>If you would like more information on writing custom interfaces, or if you would to commission MicroAPL to write an interface on your behalf, please contact MicroAPL.</p> <hr> </td> </tr> <tr> <td width="800" valign="top" colspan="2"> <center>Topic: <A HREF="ch.htm">APLX Help</A> : <A HREF="ch_070.htm">Interfacing to other languages</A> : <A HREF="ch_070_090.htm">Custom interfaces</A> </center> <center> [<A HREF="ch_070_100.htm">Next</A> | <A HREF="ch_070_060.htm">Previous</A> | <A HREF="ch.htm">Contents</A> | <A HREF="help_index.htm">Index</A> | <A HREF="http://www.microapl.co.uk/apl/index.html">APL Home</A> ]</center> <br></td> </tr> </table> <!-- %%COMMON_BODY_TAIL%% --> <p class="copyright">Copyright © 1996-2010 MicroAPL Ltd</p> <!-- %%END%% --> </body> </html>