2015-01-30 12:57 GMT+02:00 Elias Mårtenson <loke...@gmail.com>:
> I already do pretty much this in the Android version. The Android APK
> contains libapl.so which is then linked from the Java code which drives the
> user interface.
>
> Building libapl.so takes a bit of manual work right now, but in essence I
> configure the GNU APL source using the --with-android flag, and then compile
> and manually link the library together with some glue code.
>
> You can look at the source here:
> https://github.com/lokedhs/android-gnu-apl/tree/master/build-tools
Thanks. I'll look at that.
In the meantime, I have discovered one bug in Workspace.hh.
Lines 73–75 say:
/// set the current Quad-CT
static void set_CT(APL_Float new_CT)
{ the_workspace.v_Quad_FC.current(); }
However, new_CT is not used in the body of the procedure
and Quad-CT is unchanged.
Regards.
Dirk
