<abu[m]>
But I also don't understand the throw at the end of the loop
<abu[m]>
The loop never loops then?
<tankf33der>
yea
<tankf33der>
every throw is loop kiiller
<abu[m]>
yes, so the loop is not needed? A 'cond' would do, no?
<tankf33der>
i will think
<tankf33der>
old code, i do remember details
<tankf33der>
old code, i do not remember details
<abu[m]>
It is ok, just interesting way :)
<tankf33der>
check pseudocode in README.md file
<abu[m]>
throws are the translations of the return statements
<tankf33der>
i think so
<tankf33der>
i think so now
<abu[m]>
yeah, no problem, catch/throw are a bit expensive, so not really needed here
<abu[m]>
Do you experiment with crypto key generation?
<tankf33der>
then i should think and check code again
<tankf33der>
no
<abu[m]>
Sometimes pseudocode is a bit strange
<tankf33der>
From internet
<tankf33der>
cut catch-throw is challenge
<abu[m]>
I don't think so, as 'loop' is also not needed
<abu[m]>
Just exit the 'do' with a 'T'?
<tankf33der>
there are two loops
<tankf33der>
one repeat and second inside
<tankf33der>
and i should exit from inside loop to outside
<tankf33der>
i will think and try.
<abu[m]>
Yeah, a bit tricky
<abu[m]>
The (do P ..) must be exited
<tankf33der>
good i have test suite.
<abu[m]>
I think the basic structure is something like http://ix.io/443A
<abu[m]>
Probably not correct conditions, but the flow
<abu[m]>
But catch/throw is not bad, as it needs to exit from a loop with a conditional inside, so for clarity you might as well keep it
<tankf33der>
i know this flow
<tankf33der>
your code failed on tests.
<tankf33der>
i do not have energy anyway.
<abu[m]>
Yes, of course, as I said the conditions are probably wrong
<abu[m]>
Think about it step by step
<abu[m]>
(or (=1 X) (= X N1))) then 'do' continues, right?
<tankf33der>
afk.
razzy has joined #picolisp
<razzy>
hello, i wonder if i could easily have history of command from vip command line or C-e evaluation. thank you. :]
<abu[m]>
Hi razzy!
<razzy>
afk, will read later.
razzy has quit [Quit: leaving]
<abu[m]>
Well, the command window *is* a history
<abu[m]>
Then there is TAB expansion which also looks up the history of the underlying PicoLisp REPL
<abu[m]>
Line 996 in @lib/vip.l : (chop (car (rot (setq *Complete (history)))))
rob_w has quit [Remote host closed the connection]
<anddam>
tankf33der: I might believe you, but I am in no position to speak ill of SICP
<anddam>
and too many sources have praised it for me not to read it
<beneroth>
well popularity is a weak indicator of quality at best
<beneroth>
otherwise I agree with your statement. I think I started reading SICP at one point but it just didn't apply to my needs and concerns.
<abu[m]>
Probably it is a good book. The point is only that it is useless for PicoLisp
<beneroth>
abu[m], how are you faring with matrix now?
<abu[m]>
Now it works perfectly
<abu[m]>
There was a Debian packaging bug a few weeks ago, so I temporarily installed from unstable
<beneroth>
hahaha
<beneroth>
sounds still very immature to me.
<beneroth>
and I still don't get the purpose versus a simple IRC client. Of course it can be a client for multiple chat systems in one (but then why not pidgin...), but all the features only really make sense if the other end is also using matrix, right?
<abu[m]>
For me the reason is that I get a notification without keeping my IRC client open
<beneroth>
well, if it's just that.. sounds like an idea for pilbox :P
<abu[m]>
true
<abu[m]>
The Debian packaging problem was not Matrix's fault. It was a typical Python version mess.