<Hunar>
Hi Regenaxer, I did :) but I didn't see %80 of the screen shares
<Regenaxer>
Yeah, this is a problem. Let's concentrate on SSH sessions next time, that is more reliable and readable
<Hunar>
I didn't understand what SSH session is, my only experience with ssh is a remote access to a server
<Regenaxer>
yes, exactly that
<Regenaxer>
I open an ssh session with tmux where everybody can connect to in a read-only mode
<Hunar>
Ah, that's new to me :) I'll check it out later
<Hunar>
I have a small problem, I want to ask and get input from the user, i tried this (prin "a: ") (setq a (read)) (prin "b: ") (setq b (read)) which the output suggest is the wrong way to do such a thing.. in CL there was (readline) for user input
<Regenaxer>
You mean (read) is not what you want?
<Regenaxer>
Then (line) or (line T) ?
<Hunar>
when I run that (my code) the value of a is (prin "b")
<Regenaxer>
Yes, if you do that in a file
<Regenaxer>
This is because the current input channel is *this* file
<Regenaxer>
If you want to read from stdin, do
<Regenaxer>
(in NIL (read))
<Regenaxer>
(in NIL (line))
<beneroth>
NIL = stdin/stdout
<Regenaxer>
yep
<Hunar>
(in NIL (prin "a") (setq a (read)) (prin "b") (setq b (read))) This worked, but (line) returns string, I currently want a number so i used (read)
<Regenaxer>
yes, (read) is fine
<Hunar>
:D Thanks
<Hunar>
Have you tried compiling miniPicoLisp on termux? I just tried it for no reason and it fails.. https://ibb.co/bLfxLNp
<Regenaxer>
Yes, known issue with clang
<Regenaxer>
variable size arrays
<Regenaxer>
stupid compiler!
<Hunar>
Is there a compiler flag to ignore those issues?
<Regenaxer>
The other are all (equally stupid) warnings
<Regenaxer>
No, clang will "never" support variable arrays
<Regenaxer>
As I said, stupid
<Hunar>
Oh :(
<Regenaxer>
Needs another compiler like gcc
<Regenaxer>
same issue with pil32
<Regenaxer>
pil64 is not an issue cause it is not C