|
From: | Juergen Sauermann |
Subject: | Re: [Bug-apl] )IN crashes |
Date: | Mon, 16 Jun 2014 16:26:45 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130330 Thunderbird/17.0.5 |
Hi David,
it is generally impossible in APL to check if a function uses a feature or not. For example A ⎕CR B may or may not use dyadic ⎕CR (which is a GNU APL extension), depending on whether A is a variable or a function. And )OUT simply dumps the function's ⎕CR without further analyzing it. /// Jürgen On 06/15/2014 09:45 PM, David B. Lamkins wrote: Thank you. Confirmed working. On a related note: would it make sense to also warn about other GNU APL extensions when writing an )OUT file? I'm thinking in particular of lambdas and defined-function axis notation; these don't seem to cause problems with )OUT and )IN, but neither are they standard APL notation. On Sun, 2014-06-15 at 16:19 +0200, Juergen Sauermann wrote:Hi David, thanks for isolating the fault. I fixed it in SVN 327. The fault was created by native functions being )OUT-ed and )IN-ed. They are now handled properly, but the file created by )OUT is no longer suitable as workspace exchange file when it contains native functions (because native functions are a GNU APL extension that will not be understood by other APL interpreters). )OUT issues a warning for every native function being written. |
[Prev in Thread] | Current Thread | [Next in Thread] |