Hi Oskar,
But this is not the point because you're going to loose unsaved data
and the error could also be caught somewhere else.
This is right. These errors are just signals, which could be easily
added to the signal handler (just extend sighandler() in src/main.c or
'sighandlerE' in
Hi Alex,
thanks for your answer. It is a great pleasure to see how PicoLisp works...
In general, PicoLisp doesn't catch such errors, as this would induce
relatively high runtime overhead, in contrast to their extremely rare
occurrence in production programs.
I agree and I did not expect it.
On Sun, May 19, 2013 at 11:03 AM, Oskar Wieland oskar.wiel...@gmx.de wrote:
It doesn't check at runtime for all possible error conditions which won't
occur during normal usage.
What is normal usage?
Normal usage means you are running a program which is written
following the rules described in
Yes, the FAQ should definitely elaborate on that, since people are used to
that interpreted languages can not induce segfaults on their own. Also explain
perhaps that the interpreter could check all C calls against a white list, but
it would take a lot of time
Alexander Burger
On Fri, May 17, 2013 at 08:14:12AM +0200, Jakob Eriksson wrote:
Yes, the FAQ should definitely elaborate on that, since people are
Yes, Jakob, I'll add some explanation. Roughly along the line what I
wrote in the mail. Should make things a little clearer.
used to that interpreted languages
and it was a perfectly clear explanation.
no the question is where should it go within the docs?
just put this example under the faq#segfault?
(which, btw, crashed my chrome on the 1st load, but worked on reload ;)
--
tom
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
On Fri, May 17, 2013 at 02:30:19PM +0800, Tamas Herman wrote:
no the question is where should it go within the docs?
just put this example under the faq#segfault?
I thought so. Is there a better place?
(which, btw, crashed my chrome on the 1st load, but worked on reload ;)
Just tried it
Hi Oskar,
bitte melde mich fuer die email liste an.
Sure! It happened automatically already :)
: (setq foo 1)
- 1
: (foo)
Segmentation fault (core dumped)
I understand your worries, but this is actually a feature.
In general, PicoLisp doesn't catch such errors, as this would induce
