picolisp  

Messages by Thread

• • Re: PilCon 2020 r cs
  • Re: PilCon 2020 Brian Cleary
  • Re: PilCon 2020 Alexander Shendi (Web.DE)
  • Re: PilCon 2020 Jean-Christophe Helary
  • Re: PilCon 2020 George-Phillip Orais
  • Re: PilCon 2020 Wilhelm Fitzpatrick
  • Re: PilCon 2020 Wojciech Gac
  • Re: PilCon 2020 cilz
  • Re: PilCon 2020 Edgaras Šeputis
  • Re: PilCon 2020 andreas
  • Re: PilCon 2020 Mattias Sundblad
  • Re: PilCon 2020 O.Hamann
  • Re: PilCon 2020 Bruno Franco
  • Re: PilCon 2020 Kevin Ednalino
  • Re: PilCon 2020 Tomas Hlavaty
  • Re: PilCon 2020 Grant Shangreaux
  • Re: PilCon 2020 Jean-Christophe Helary
  • Re: PilCon 2020 Alexander Burger
  • Re: PilCon 2020 Alexander Shendi (Web.DE)
  • Re: PilCon 2020 Jean-Christophe Helary
  • Re: PilCon 2020 Alexander Shendi (Web.DE)
  • Re: PilCon 2020 Wojciech Gac
  • Re: PilCon 2020 Jean-Christophe Helary
  • Re: PilCon 2020 Jean-Christophe Helary
  • Re: PilCon 2020 Christophe Gragnic
  • Re: PilCon 2020 Jean-Christophe Helary
  • Re: PilCon 2020 Christophe Gragnic
  • Re: PilCon 2020 Tomas Hlavaty
  • Re: PilCon 2020 O.Hamann
  • Re: PilCon 2020 Guido Stepken
• MiniPicolisp Questions C K Kashyap
  • Re: MiniPicolisp Questions Alexander Burger
  • Re: MiniPicolisp Questions C K Kashyap
  • Re: MiniPicolisp Questions Alexander Burger
  • Re: MiniPicolisp Questions C K Kashyap
  • Re: MiniPicolisp Questions Guido Stepken
  • Re: MiniPicolisp Questions George-Phillip Orais
  • Re: MiniPicolisp Questions Alexander Burger
  • Re: MiniPicolisp Questions Guido Stepken
  • Re: MiniPicolisp Questions Alexander Burger
  • Re: MiniPicolisp Questions Guido Stepken
  • Re: MiniPicolisp Questions C K Kashyap
  • Re: MiniPicolisp Questions Alexander Burger
  • Re: MiniPicolisp Questions C K Kashyap
  • Re: MiniPicolisp Questions C K Kashyap
  • Re: MiniPicolisp Questions Guido Stepken
  • Re: MiniPicolisp Questions George-Phillip Orais
  • Re: MiniPicolisp Questions Guido Stepken
• Why i chose PicoLisp as main language for my projects ... Guido Stepken
• Stop using US controlled software stacks!!! Guido Stepken
  • Re: Stop using US controlled software stacks!!! andreas
  • Re: Stop using US controlled software stacks!!! George-Phillip Orais
  • Re: Stop using US controlled software stacks!!! Guido Stepken
  • Re: Stop using US controlled software stacks!!! George-Phillip Orais
  • Re: Stop using US controlled software stacks!!! Alexander Burger
  • Re: Stop using US controlled software stacks!!! George-Phillip Orais
  • Re: Stop using US controlled software stacks!!! Guido Stepken
  • Re: Stop using US controlled software stacks!!! Tomas Hlavaty
  • Re: Stop using US controlled software stacks!!! Guido Stepken
  • Re: Stop using US controlled software stacks!!! Tomas Hlavaty
  • Replace LLVW - Was: Stop using US controlled software stacks!!! Alexander Burger
  • Re: Replace LLVW - Was: Stop using US controlled software stacks!!! Guido Stepken
  • Re: Replace LLVW - Was: Stop using US controlled software stacks!!! George-Phillip Orais
  • Re: Stop using US controlled software stacks!!! Tomas Hlavaty
  • Re: Stop using US controlled software stacks!!! Guido Stepken
  • Re: Stop using US controlled software stacks!!! Tomas Hlavaty
  • Re: Stop using US controlled software stacks!!! Alexander Burger
  • Re: Stop using US controlled software stacks!!! Guido Stepken
  • Re: Stop using US controlled software stacks!!! Alexander Burger
  • Re: Stop using US controlled software stacks!!! Guido Stepken
  • Re: Stop using US controlled software stacks!!! Jo-To Schäg
  • Re: Stop using US controlled software stacks!!! Guido Stepken
  • Re: Stop using US controlled software stacks!!! Tomas Hlavaty
  • Re: Stop using US controlled software stacks!!! Jeronimo Pellegrini
  • Re: Stop using US controlled software stacks!!! Guido Stepken
  • Re: Stop using US controlled software stacks!!! Jean-Christophe Helary
  • Re: Stop using US controlled software stacks!!! Tomas Hlavaty
  • Re: Stop using US controlled software stacks!!! Jeronimo Pellegrini
  • Re: Stop using US controlled software stacks!!! Tomas Hlavaty
  • Re: Stop using US controlled software stacks!!! Alexander Shendi (Web.DE)
  • Re: Stop using US controlled software stacks!!! Tomas Hlavaty
  • Re: Stop using US controlled software stacks!!! Tomas Hlavaty
  • Re: Stop using US controlled software stacks!!! Guido Stepken
  • Re: Stop using US controlled software stacks!!! Danilo Kordic
  • Re: Stop using US controlled software stacks!!! Guido Stepken
  • Re: Stop using US controlled software stacks!!! Wilhelm Fitzpatrick
  • Re: Stop using US controlled software stacks!!! Edgaras Šeputis
  • Re: Stop using US controlled software stacks!!! Guido Stepken
  • Re: Stop using US controlled software stacks!!! Guido Stepken
  • Re: Stop using US controlled software stacks!!! rick
  • Re: Stop using US controlled software stacks!!! Guido Stepken
• picoLisp 19.12: variable length array in structure fixes Andras Pahi
  • Re: picoLisp 19.12: variable length array in structure fixes Alexander Burger
  • Re: picoLisp 19.12: variable length array in structure fixes Alfonso Villén
  • Re: picoLisp 19.12: variable length array in structure fixes Mike
  • Re: picoLisp 19.12: variable length array in structure fixes George-Phillip Orais
  • Re: picoLisp 19.12: variable length array in structure fixes Andras Pahi
  • Re: picoLisp 19.12: variable length array in structure fixes Mike
  • Re: picoLisp 19.12: variable length array in structure fixes Andras Pahi
  • Re: picoLisp 19.12: variable length array in structure fixes Mike
  • Re: picoLisp 19.12: variable length array in structure fixes Guido Stepken
  • Re: picoLisp 19.12: variable length array in structure fixes Andras Pahi
  • Re: picoLisp 19.12: variable length array in structure fixes Alexander Burger
  • Re: picoLisp 19.12: variable length array in structure fixes C K Kashyap
  • Re: picoLisp 19.12: variable length array in structure fixes Mike
  • Re: picoLisp 19.12: variable length array in structure fixes Andras Pahi
  • Re: picoLisp 19.12: variable length array in structure fixes Mike
  • Re: picoLisp 19.12: variable length array in structure fixes Guido Stepken
• Latest pil21 under OpenBSD 6.6-STABLE Alexander Shendi (Web.DE)
  • Re: Latest pil21 under OpenBSD 6.6-STABLE Alexander Burger
  • Re: Latest pil21 under OpenBSD 6.6-STABLE rick
  • Re: Latest pil21 under OpenBSD 6.6-STABLE Alexander Shendi (Web.DE)
  • Re: Latest pil21 under OpenBSD 6.6-STABLE Alexander Burger
• Tiny C Compiler C K Kashyap
  • Re: Tiny C Compiler Guido Stepken
  • Re: Tiny C Compiler C K Kashyap
  • Re: Tiny C Compiler Guido Stepken
• pastebin service Mike
• pil21 language reference? Alexander Shendi (Web.DE)
  • Re: pil21 language reference? Alexander Burger
  • Re: pil21 language reference? Guido Stepken
  • Re: pil21 language reference? Alexander Burger
• Interning symbols in lib/simul.l Bruno Franco
  • Re: Interning symbols in lib/simul.l Alexander Burger
  • Re: Interning symbols in lib/simul.l Mike
  • Re: Interning symbols in lib/simul.l Bruno Franco
• Did you know? Webassembly Containers are (Pico-)Lisp machines! Guido Stepken
  • Re: Did you know? Webassembly Containers are (Pico-)Lisp machines! Rowan Thorpe
  • Re: Did you know? Webassembly Containers are (Pico-)Lisp machines! Tomas Hlavaty
  • PicoLisp Sources Alexander Burger
  • Re: PicoLisp Sources Guido Stepken
  • Re: PicoLisp Sources Guido Stepken
  • Re: PicoLisp Sources Tomas Hlavaty
  • Re: PicoLisp Sources George-Phillip Orais
  • Re: PicoLisp Sources Alexander Burger
  • Re: PicoLisp Sources George-Phillip Orais
  • Re: PicoLisp Sources Alexander Burger
  • Re: PicoLisp Sources Tomas Hlavaty
  • Re: Did you know? Webassembly Containers are (Pico-)Lisp machines! Alexander Burger
  • Re: Did you know? Webassembly Containers are (Pico-)Lisp machines! Guido Stepken
  • Re: Did you know? Webassembly Containers are (Pico-)Lisp machines! Alexander Burger
  • Re: Did you know? Webassembly Containers are (Pico-)Lisp machines! Guido Stepken
  • Re: Did you know? Webassembly Containers are (Pico-)Lisp machines! Alexander Burger
  • Re: Did you know? Webassembly Containers are (Pico-)Lisp machines! Guido Stepken
  • Pil21 on NetBSD9/aarch64 Alexander Shendi (Web.DE)
  • Re: Pil21 on NetBSD9/aarch64 Alexander Burger
  • Re: Pil21 on NetBSD9/aarch64 Alexander Shendi (Web.DE)
  • Re: Pil21 on NetBSD9/aarch64 Alexander Burger
  • Re: Pil21 on NetBSD9/aarch64 Alexander Shendi (Web.DE)
  • Re: Pil21 on NetBSD9/aarch64 Alexander Burger
  • Re: Pil21 on NetBSD9/aarch64 Alexander Shendi (Web.DE)
  • Re: Pil21 on NetBSD9/aarch64 Alexander Burger
  • Pil21 on OpenBSD 6.6-STABLE Alexander Shendi (Web.DE)
  • Pil21 on Linux Mint/aarch64 Karl-Heinz Kreis
  • Re: Pil21 on Linux Mint/aarch64 Alexander Burger
• Lisp, a language for "Stratified Design" Podcast and paper.pdf Guido Stepken
  • Re: Lisp, a language for "Stratified Design" Podcast and paper.pdf C K Kashyap
  • Re: Lisp, a language for "Stratified Design" Podcast and paper.pdf George Orais
• 回复：Towards a more readable Pico(Lisp) ... nobody needs parenthesis! Enwei Zhang
• Towards a more readable Pico(Lisp) ... nobody needs parenthesis! Guido Stepken
  • Re: Towards a more readable Pico(Lisp) ... nobody needs parenthesis! andreas
  • Re: Towards a more readable Pico(Lisp) ... nobody needs parenthesis! Jean-Christophe Helary
  • Re: Towards a more readable Pico(Lisp) ... nobody needs parenthesis! clacke
  • Re: Towards a more readable Pico(Lisp) ... nobody needs parenthesis! Guido Stepken
• Porting Picolisp onto the simplest possible processor - The new SISC! Guido Stepken
  • Re: Porting Picolisp onto the simplest possible processor - The new SISC! andreas
  • Porting Picolisp onto the simplest possible processor - The new SISC! Guido Stepken
  • Re: Porting Picolisp onto the simplest possible processor - The new SISC! andreas
  • Re: Porting Picolisp onto the simplest possible processor - The new SISC! Alexander Burger
  • Re: Porting Picolisp onto the simplest possible processor - The new SISC! Guido Stepken
• 64bit miniPicoLisp C K Kashyap
  • Re: 64bit miniPicoLisp Alexander Burger
  • Re: 64bit miniPicoLisp C K Kashyap
• miniPicoLisp/picoLisp difference C K Kashyap
  • Re: miniPicoLisp/picoLisp difference Alexander Burger
  • Re: miniPicoLisp/picoLisp difference C K Kashyap
• minipicolisp with Microsoft C compiler C K Kashyap
  • minipicolisp with Microsoft C compiler C K Kashyap
  • Re: minipicolisp with Microsoft C compiler Alexander Burger
• Vip screen resize Wojciech Gac
  • Re: Vip screen resize Alexander Burger
  • Re: Vip screen resize Wojciech Gac
  • Re: Vip screen resize Alexander Burger
  • Re: Vip screen resize Мансур Мамкин
  • Re: Vip screen resize Wojciech Gac
• Turtle graphics Alfonso Villén
  • Re: Turtle graphics Alexander Burger
• Small Docker container builds the latest pil in Alpine image David Bloom
  • Re: Small Docker container builds the latest pil in Alpine image Guido Stepken
  • Re: Small Docker container builds the latest pil in Alpine image andreas
  • Re: Small Docker container builds the latest pil in Alpine image David Bloom
  • Re: Small Docker container builds the latest pil in Alpine image Guido Stepken
  • Re: Small Docker container builds the latest pil in Alpine image David Bloom
• Review request for the patch for 64bit compilation of miniPicoLisp C K Kashyap
  • Re: Review request for the patch for 64bit compilation of miniPicoLisp Alexander Burger
  • Re: Review request for the patch for 64bit compilation of miniPicoLisp C K Kashyap
  • Re: Review request for the patch for 64bit compilation of miniPicoLisp Alexander Burger
  • Re: Review request for the patch for 64bit compilation of miniPicoLisp C K Kashyap
• Bug in rand Alfonso Villén
  • Re: Bug in rand Alexander Burger

• Earlier messages
• Later messages