Hi,
Kacper is right - it is in the standard.
But the standard merely says "Set the rest of event-message as appropriate".
The rest is rather APL2 specific. I could also argue that the current
value of the parameter
is more relevant to the exception than the original value. I have put
this int
Got it. Thanks.
On Mon, Jul 14, 2014 at 11:44 AM, Kacper Gutowski
wrote:
> Whoops, this thread was about the message rather than return value.
> About that, standard states that event-message is local to a context and
> that ⎕ES should create an exception in caller's context, but I don't
> thi
Whoops, this thread was about the message rather than return value.
About that, standard states that event-message is local to a context and
that ⎕ES should create an exception in caller's context, but I don't
think it's properly specified what does it exactly mean.
But the point is, that ⎕ES _is_
Dear Juergen,
Every place that I use ⎕ES I am being forced to treat the arguments as
read-only. I also had to re-order code to account for optional arguments.
It makes for some ugly code. I hope when you add lazy copying of arrays,
the internal code to do this correctly won't be a problem.
Show
That "return nil" is clearly a typo and a further reflection of the poor
quality of that spec. I offer the following as proof that that comment is
a typo:
1. Look at the signature of ⎕ES at the beginning of 11.5.7. It says:
⎕ES B
it does not say:
Z←⎕ES B
like they do everywhere el
On 2014-07-14 16:15:32, Juergen Sauermann wrote:
> Since ⎕ES is not ISO-standard anyhow, I take the freedom to trade performance
> for APL2 compatibility.
But it is. See sections 11.5.7 and 11.6.5.
And standard says it should return nil for empty right
argument, which means not returning any valu
Jürgen,
Do you think it would be possible to implement some way of retrieving not
only the error code, but also the )MORE text from an exception inside
an ⎕EA?
The reason for this is that in my SQL∆WithTransaction call, I need to call
the rollback function if there is an error, but then I want to
Hi Blake,
I believe the ⎕ES related bugs reported recently should be fixed in SVN 372.
This one is not, though. The reason is that fixing it would have
considerable performance
impacts (we would need a copy of every defined function argument only
for the rare case that ⎕ES
is called),
I also
)CLEAR
CLEAR WS
∇test x
[1] x←'xx'
[2] ⎕ES 'SOME ERROR'
[3] ∇
test '55'
SOME ERROR
test 'xx'
^ ^
⎕ES is showing the modified and not the original argument passed to the
function. IBM APL 2 displays the original argument passed.
Thanks.
Blake
