If you search your email you'll find that we've touched on this subject
before.
Complex residue (aka remainder, modulo) is defined the same as for real
numbers: assuming you already have a complex floor operation then Residue
←{⍵-⍺×⌊⍵÷⍺}.
Complex floor is a complex subject, especially when you
in
Hi APLers,
first let me thank, for that wonderful piece of software!
Using the ∇-editor I found some inconsistencies, perhaps a bug or am I
using ∇ wrong? Reference APL2 docu and Nabla.cc:
" // we expect one of the following:
//
// [⎕] [n⎕] [⎕m] [n⎕m] [⎕n-m](show)
//
Hi Alexander,
the _N issue is fixed in SVN 1253.
Regarding the warning there seems to be a mismatch in the
determination
of the memory available to the process running the interpreter. The
methods
for doing that are potentially platform specific.
Hi Otto,
thanks for reporting this. I guess I simply missed that case.
Fxed in *SVN 1254*.
Best Regards,
Jürgen Sauermann
On 4/8/20 12:13 PM, Otto Diesenbacher-Reinmüller wrote:
> Hi APLers,
>
> first let me thank, for that wonderful piece of software!
>
> Using the ∇-editor I found some incon
Hi again,
I would also like to point out that recursive use of ∇ (editing another
function
while editing a function) is supported in APL2 but not in GNU APL (and there
are no plans to change that).
Best Regards,
Jürgen
On 4/8/20 1:38 PM, Dr. Jürgen Sauermann wrote:
> Hi Otto,
>
> thanks for rep
OpenBSD does not have the /proc filesystem.
What does cat /proc/meminfo do? So that I can provide an analogous
OpenBSD command.
~Brian
On 2020-04-08 6:58 AM, Dr. Jürgen Sauermann wrote:
Hi Alexander,
the _N issue is fixed in *SVN 1253*.
Regarding the warning there seems to be a mismatch in
Heres the contents of /proc/meminfo on linux 5.4.0-2-amd64:
MemTotal:7833580 kB
MemFree: 949240 kB
MemAvailable: 997536 kB
Buffers: 108 kB
Cached: 1062792 kB
SwapCached: 532548 kB
Active: 3367828 kB
Inactive:2045752 kB
Active(anon):
Greetings,
Look at the formatting. In particular look at how the lines with labels
and comments are indented. They are indented differently depending on
whether the file is saved or dumped.
∇ABC[⎕]∇
∇
[0] ABC
[1] X←4
[2] EN1: Y←5
[3] Z←7
[4] ⍝ THIS IS A COMMENT
[5] Z←5
∇
Hi Dr. Sauermann,
I'm supplying the desired info:
1. Output of "ulimit -a"
time(cpu-seconds)unlimited
file(blocks) unlimited
coredump(blocks) unlimited
data(kbytes) 6291456
stack(kbytes)4096
lockedmem(kbytes)2671438
memory(kbytes) 8010120
nofiles(descrip
Greetings,
Echoing some thoughts I've had on this subject, given the trouble we've had
with function formatting over the years between the del editor and ⎕CR, I
get the impression that function formatting is occurring at the wrong
place. I think internally functions should be stored left-justifie
Lastly, I should mention that the first display of ABC is the correct one,
and the one that matched IBM APL.
Thanks.
Blake
On Wed, Apr 8, 2020 at 8:46 AM Blake McBride wrote:
> Greetings,
>
> Echoing some thoughts I've had on this subject, given the trouble we've
> had with function formattin
)clear
CLEAR WS
)save xx
NOT SAVED: THIS WS IS CLEAR WS
)wsid xx
WAS CLEAR WS
)save
2020-04-08 09:11:35 (GMT-5) xx
The first save should have, effectively, done the )wsid for me.
Thanks.
Blake
Also, and further showing the point that the formatting is occurring at the
wrong place:
⎕CR 'ABC'
ABC
x←4
EN1: Y←5
Z←7
⍝ THIS IS A COMMENT
Z←5
Those space characters before each line should never happen but does when
the file is loaded from a .APL file.
Thanks!
Blake
On Wed, Ap
Dear Dr. Sauermann,
I just realised that you might mean 'apl -l 37'.
Here ist the output of that command.
initial RLIMIT_AS (aka. virtual memory) is: 6442450944
estimated available memory: 3221225472 bytes (3221 MB)
*** Warning: the process memory limit (RLIMIT_AS) of 6442450944
is more than the
Hi Jürgen,
many thanks for that super-quick fix!
I can confirm, works fine.
Just a minor bug remains: calling [→] for a new function results in an
exception, see below.
br & many thanks - Otto
)clear
CLEAR WS
)fns
∇test
[1] ⍝ a teste...
[2] [→]
Hi Alexander,
thanks for the info. The -l37 option requres that you
either:
./configure
DYNAMIC_LOG_WANTED=yes
or:
make develop
after ./configure and before make install.
The background of all
Hi Otto,
thanks, fixed in SVN 1255.
Best Regards,
Jürgen
On 4/8/20 5:05 PM, Dr. Jürgen Sauermann
wrote:
Hi Alexander,
thanks for the info. The -l37 option requres that you
either:
./
Hi Otto,
thanks, fixed in *SVN 1255*.
Best Regards,
Jürgen
On 4/8/20 5:04 PM, Otto Diesenbacher-Reinmüller wrote:
> Hi Jürgen,
>
> many thanks for that super-quick fix!
>
> I can confirm, works fine.
>
> Just a minor bug remains: calling [→] for a new function results in an
> exception, see bel
Hi Blake,
thanks, hopefully fixed in SVN 1256.
Best Regards,
Jürgen
On 4/8/20 4:18 PM, Blake McBride wrote:
Also, and further showing the point that the
formatting is occurring at the wrong place:
Thanks. While it appears to work, it's clearly wrong. The formatting is
still being done at the wrong place. The way I discovered this is to load
a .apl file from a prior version of GNU APL. When I list the function,
it's wrong. So, GNU APL is depending on the format in the file rather than
ha
Greetings,
David Lamkins' package manager was dropped from his GitHub account. I
received the latest version from David and re-posted it to my GitHub
account with his permission.
https://github.com/blakemcbride/APL-Pkg
Thanks.
Blake McBride
Hi Blake,
the problem is that there are no rules for the formatting of the
functions. I know
that you had a few proposals in the past, but I haven't found a
proper mental model
of how to handle this.
Please note that the .apl files are no
Hi Blake,
I was thinking of this but then discarded it. Storing functions
left-justified would
loose all indentation of the code:
* ∇foo**
**[1] 1**
**[2] 2**
**[3] 3**
**[4] ∇**
**
** ⎕CR 'foo'**
**foo**
**1 **
** 2 **
** 3*
I know that currently indentation of defined fu
Hi Jürgen,
How about this for a set of rules:
1. Format .apl and .XML files any way you like.
2. Regardless of how a function is instantiated (.apl, .XML, ⎕FX, the del
editor) the internal representation is all lines left-justified. Leading
and trailing spaces for each line from the source ar
Hi Blake,
IMHO it should not because the )save xx has failed. If it
had
succeeded, then the wsid would have been changed.
The reason why it failed is probably because the file xx
already existed. This is a safeguard against accidental
override o
Hi Blake,
I could live with 1. and 3. (which can be fixed in ⎕CR alone).
However, 2. is not needed for this and it conflicts with 1. because
at least the .xml files store the internal representation in XML format.
The IBM ∇-editor is quite rigid in removing indentation but
I rather see that as a
Greetings,
With David Lamikins' permission, I have moved his GitHub APL repos to my
own repo for public consumption. The following packages are available:
https://github.com/blakemcbride/APL-Sha256 SHA256 for GNU APL
https://github.com/blakemcbride/akt Keyboard handling for GNU APL
https://gi
Hi,
As far as I am aware, the del editor displays functions as you do -
including the indenting of labels and comments. Yes, it helps looking at
code. I am certainly not suggesting changes to that! The point is that
the del editor can add that formatting when displaying a function. That
format
28 matches
Mail list logo
