Hi Elias,
I have added an item in ⎕SYL that cuts down APL value when printed as
non-committed value
(i.e. as statement result). SVN 253.
/// 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 implemented?
On Wed, 2014-04-30 at 17:29 +0200, 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 the number of ravel bytes. This was to
> limit infinite recursion of
> user-defined functions. When su
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