The following gives a syntax error:
*((1 1) (1 0))/¨'ab' 'cd'*
SYNTAX ERROR
(1 1) (1 0)/¨'ab' 'cd'
^ ^
But, assuming the following function:
∇Z←X sel Y
Z←X/Y
∇
This works:
*((1 1) (1 0))sel¨'ab' 'cd'*
ab c
Regards,
Elias
Hi Fred,
when designing derived functions I had the choice between a faster
variant that
uses pre-allocated memory for derived functions and a somewhat slower
variant
that uses dynamic memory allocation (i.e. new/delete directly or
indirectly (eg. vector<>)).
Since this happens on a performa
Hi,
thanks, fixed in SVN 118.
/// Jürgen
On 02/02/2014 01:19 PM, ds.jaypee wrote:
Environment:
- GNU APL 1.2 or latest checkout from SVN, built from source
- OS X Mavericks, MacBookPro 8 GB RAM, More than 10 GB free disk space
Workspace,
- Manually edited and tested on Dyalog APL,
- Exported
On 2014-02-12 12:58:05, Elias Mårtenson wrote:
> The key feature that is needed is a way to be informed when a variable is
> changed.
Shared variables have such feature. Though, it's probably not the right
place for you too look in this case, as shared variables are whole separate
name class and
Hello,
There are multiple problems with shared variables facility.
1. Shared variable protocol is not safe in multi user environment.
When user starts apl with shared variables enabled, it removes all
other users' sessions from shared database as “stale” so currently
even honest user without mal
My Emacs mode already uses the external function editor. You access it
using C-c C-f. What I did was also to detect when ∇ is typed, and intercept
that command to also open up the function editor that way. Thus, right now,
there are two ways to open the function editor in Emacs.
The reason I did t
Function definition mode (typing ∇ followed by a symbol name) is an
artifact of the kind of terminal hardware supported by APL (the IBM
2741 with its iconic typeballs) in the 1960s. As such, nearly 50
years later, it may be worth rethinking some of these things to take
advantage of newer editor a
Right now, the Emacs mode preprocesses all input being typed by the user,
and if he types ∇ followed by a symbol name, the external function editor
is opened and the command is never actually sent to the interpreter. This
works fairly well, but there are some annoyances:
- Emacs doesn't know if
