Hi Peter,
sorry as well. I believe i was mislead by your earlier question for the
source of the Nabla editor.
I cannot give you a full answer because the question touches many aspects
of GNU APL, like how to do things, who does and maintain things, what do
we like,
and so on.
But I can share
Hi,
I am sayng that a mechanism exist and may be suitable (or not).
The actual limits (array size in printed values) would need to be added.
/// Jürgen
On 04/30/2014 05:30 PM, Elias Mårtenson wrote:
Are you saying that this limit exists, or that it's something that
would have to be implemente
Are you saying that this limit exists, or that it's something that would
have to be implemented?
Regards,
Elias
On 30 April 2014 23:29, Juergen Sauermann wrote:
> Hi,
>
> maybe some ⎕SYL limit could work. Currently we have such limits on the
> depth of the SI,
> on the number of values, and on
Hi,
maybe some ⎕SYL limit could work. Currently we have such limits on the
depth of the SI,
on the number of values, and on the number of ravel bytes. This was to
limit infinite recursion of
user-defined functions. When such a limit is reached then an ATTENTION
is thrown and you can decide
to
Sometimes, I accidentally make a mistake in interactive mode that causes
GNU APL to try to render a very large array to the screen. This can cause
the pretty-printer to essentially hang for very long amounts of time, and
this operation can't be interrupted. I usually have to kill the APL
session, l
Here is what I get:
]xterm off
]log 32
Log facility 'Prefix parser ' is now ON
]log 33
Log facility ' ... location information ' is now ON
'libemacs' ⎕FX 'EMACS'
changed to Prefix[si=0])
Hi Jürgen:
So sorry but we are not understanding each other on this.
I apologize for my inability to state it more clearly.
This is a long reply but I'm trying to explain it with words.
Too bad we can't sit down over a mug of beer (or a cup of tea) and discuss it
IRL.
My proposal is NOT specific
Hi,
Hmm - below is what I get. Elias, can you reproduce the fault easily?
I guess we can rule out the archive (]log 39) then.
I see that there is a ⎕FX so I would do ]log 32 and ]log 33 next.
/// Jürgen
eedjsa@server64:~/projects/juergen/apl-1.3/src$ ./apl
__ _ __ _
Here is what I got:
]xterm off
]log 39
Log facility ')LOAD and )SAVE details ' is now ON
'libemacs' ⎕FX 'EMACS'
EMACS
EMACS[1] 0
Network listener started. Connection information: mode:tcp addr:40663
)load Devices
Loading file /home/blake/workspaces/Dev
Got this:
EMACS_NATIVE
Network listener started. Connection information: mode:tcp addr:42335
]log 39
Log facility ')LOAD and )SAVE details ' is now ON
)load Devices
Loading file /home/blake/workspaces/Devices.xml
read_Workspace()
read_Value() vid=0
read_
I made the change you suggested (although the line number for me was 1378;
I have the latest SVN). This is what I got:
EMACS_NATIVE
Network listener started. Connection information: mode:tcp addr:32954
)load Devices
SAVED 2014-4-27 16:11:45 (GMT-5)
VALUE ERROR
auto[11] start
You don't need Emacs to reproduce. All it takes is to have the backend
active. You can start it my loading the library:
* 'libemacs' ⎕FX 'EMACS'*
and then start the server:
* EMACS[1] 0*
That's all it takes. After that it should be easy to reproduce the problem.
Regards,
Elias
On 3
Hi,
problem on my machine is that I don't have emacs installed.
And without it is difficult to reproduce. Maybe Elias can help
to narrow this down a little.
If you are not getting a "vid=" printout then the fault is probably not
where I thought it would be.
The thing is that based on the info
Isn't this just such an example?
On Wed, Apr 30, 2014 at 7:17 AM, Elias Mårtenson wrote:
> The Emacs mode should not be hiding the output on standard error. If
> anyone happens to see it do that, please let me know because that would
> mean you've come across a bug.
>
> Regards,
> Elias
> On 30
The Emacs mode should not be hiding the output on standard error. If anyone
happens to see it do that, please let me know because that would mean
you've come across a bug.
Regards,
Elias
On 30 Apr 2014 20:04, "Juergen Sauermann"
wrote:
> Hi Blake,
>
> if the problem is that stderr gets lost, th
Hi Blake,
if the problem is that stderr gets lost, then it might help if you change
Archive.cc line 1348:
CERR << "vid=" << vid << endl;
FIXME;
from CERR to COUT. That should at least show the vid that tells me where
in the
.apl file this happens. Just a guess because i am not
Hi Peter,
there are already a number of facilities in GNU APL that can be switched
on and off via ./configure, for example Assert(). See the macros in
configure.ac
that end in _WANTED to see how thjis works.
I guess what you are after is ∇-editor command [A⎕B] . I would rate the
lack of it
as
The following patch improves the performace of reading a 10k line file
using io∆readfile from several minutes down to about half a second.
The key to this was to avoid cloning the result when reading the value from
a variable. This caused functions with lots of variable dereferencing to
become inc
18 matches
Mail list logo
