[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-apl] Request for feature: Back-channel interaction

From: Elias Mårtenson
Subject: Re: [Bug-apl] Request for feature: Back-channel interaction
Date: Thu, 2 Jan 2014 18:47:40 +0800

And I have started work on a native module to provide direct access to some internals of GNU APL using a simple protocol.

The basics works right now, but I have a few questions:
  1. I have a command (EE[1]) that starts the server. I would like to pass in an array of arguments (like port number, for example). What is the correct way to read these values?
  2. Right now, I just call functions on the workspace directly, and since I do this from a separate thread, it's guaranteed that this will give us race conditions and cache coherency issues. Until a "proper" threading solution is in place, how about simply having a single lock that is held while anything is touched? (in your code, that lock would be held at all times except for when you're waiting for input by the user)
  3. Could this module be shipped as part of the GNU APL distribution? That way it would be compiled as part of the normal installation and there would be no problems installing the Emacs support.
  4. I'm building and installing GNU APL into a separate directory (i.e. not /usr/local) and I find that I have to specify the full path to the .so file when I load it with ⎕FX. Is there a correct way to load a library relative the GNU APL installation directory?

On 2 January 2014 01:47, Juergen Sauermann <address@hidden> wrote:

seems like the AM_LDFLAGS did not make it to libtool.

I have changed native/Makefile to use target-specific LDFLAGS (SVN 78).
Also fixed most of the -Wlogical-op-parentheses and -Wreturn-type warnings.

/// Jürgen

reply via email to

[Prev in Thread] Current Thread [Next in Thread]