[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: Sat, 4 Jan 2014 23:28:12 +0800

Thank you. I will do this (that is, use FX :-) ).


On 4 January 2014 23:24, Juergen Sauermann <address@hidden> wrote:

you should use Quad_FX::eval_B() for two reasons:

1. it corresponds directly to ⎕FX in APL and is therefore not likely to change its parameters.
    Userfunction::fix() has changed over time and will most likely change again when lambda's are added.

2. It provides additional information (execution properties) to the function being created.

The loc parameter is the C++ source file name and line number that called fix() (for troubleshooting purposes).
If you call fix() (and you don't according to the above) you can use the LOC macro to provide
the loc parameter, like in:

     fix(function_text, LOC);

/// Jürgen

On 01/04/2014 03:49 PM, Elias Mårtenson wrote:
Thank you!

I have another question for you:

Since I need to send a new function definition from the library, I'm trying to figure out the best way to do that. As far as I can tell, I need to call UserFunction::fix() to do this. However, what I'm not entirely sure of is if there is some extra error handling I should do first?

Secondly, the mode has the ability to update a function definition in a file. I noticed that the fix() method has a "loc" parameter. Does the file name and line number of the definition go there?


On 4 January 2014 21:59, Juergen Sauermann <address@hidden> wrote:

now it is! SVN 83.

/// Jürgen

reply via email to

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