Re: Compiling Chicken app for Windows from linux with Docker

Thank you Mario, I went straight to the wiki to add my notes while it is still fresh enough. Hope it helps others. Le 03/07/2021 à 09:48, Mario Domenech Goulart a écrit : Hi Théo and all, On Sun, 27 Jun 2021 12:34:24 +0200 Théo Cavignac wrote: After my previous mail concerning the static

Re: Compiling Chicken app for Windows from linux with Docker

Hello Vasilij, thank you for your answer ! First, here is the right docker hub link: https://hub.docker.com/r/lattay/chicken-mingw I did not realize that I send the link to my private dashboard for the image. > That does sound interesting, though I'm not sure whether this won't be an issue

Compiling Chicken app for Windows from linux with Docker

Hi all, After my previous mail concerning the static compilation in a Docker container I figured it would be nice to use the same idea to create a cross compilation environment for linux-to-windows dev. Using the cross development article on the wiki, digging through the build system a bit

Re: Actor model implementation, seeking feedback

Hi ! That's cool, actor model is very useful ! Also nng is soo cool, that would be fantastic if you could extract a standalone binding egg from your work ! How does your implementation perform in purely local single process environment where serialization and encryption are not required ?

Build static binaries of chicken apps in a docker container

Hi, I wanted to write and compile Chicken apps on my linux laptop and use them on some super computer I have access to. I naturally chose to compile static app with "csc -static main.scm -o main" which would link my app against a shared glibc version. While that is what I wanted, I

Re: Hard coded paths in csc and relocatable chicken

Hi Matt, I have been interested in this problem for other reasons, mainly because I was interested in the possibility of installing eggs in userspace while Chicken was installed through distro package manager (thus in root). Anyway, in the current states of the compiler it appears that the

Re: Port of msgpack to Chicken 5

Hi Kooda, Thank you very much. I will look into the tags and how to edit the doc myself soon. Thank you for the pointer. Le mer. 24 mars 2021 à 11:11, a écrit : > Théo Cavignac wrote: > > Hi, > > > > > > About two years ago I started a big project using Chicken a

Port of msgpack to Chicken 5

Hi, About two years ago I started a big project using Chicken and msgpack. The msgpack egg being stalled and only in C4, I ported it to C5. I tried to contact the original author on Github but he never replied (maybe he will see this mail, in which case I would be happy to hand over my

Re: Source code formatter?

The problem with pretty printer is that it is not designed for source: it does not keep comments and blank lines. It would be cool if someone cared to write an actual scheme source formater. I did not find any such tool in any implementation I know. On Mon, Jan 11, 2021 at 2:55 PM wrote: > I

Re: Behavior of #!optional

Thank you Evan. By the way I just realized that `#!optional` is specific to chicken anyway which makes this behavior a lot more viable if chicken users already use it. Cheers, Théo Le 03/03/2020 à 09:21, Evan Hanson a écrit : Hi Théo, I don't know whether there are any firm guarantees

Behavior of #!optional

Hello everyone, Quick question: is it safe to rely on the fact that positional parameters are available to definition of optional parameters default value ? In other word, is the following procedure OK or does it rely on implementation detail that may change ? (define (f a b #!optional

Re: [Chicken-users] Obscure bug with srfi-18, mailbox and coops

Thank you a lot for your help Megane and Felix, you really saved my project (I nearly abandoned it). I will add disable-interrupts to my egg file. Hopefully this project will be publishable soon ! On Wed, Aug 28, 2019 at 7:42 PM megane wrote: > > Théo Cavignac writes: > > > E

Re: [Chicken-users] Obscure bug with srfi-18, mailbox and coops

Erratum: I think it did fix the bug, I just misunderstood a different error. Is this modification of coops config viable for upstream or should I find a way to grant thread safety in my own code ? On Wed, Aug 28, 2019 at 6:17 PM Théo Cavignac wrote: > Unfortunatly it did not fixed the

Re: [Chicken-users] Obscure bug with srfi-18, mailbox and coops

Unfortunatly it did not fixed the bug to add -disable-interrupts. I still have this class of bug spawning here and there with different instances and different slots. Is there a way I could protect slot access from race conditions directly in my code so that I identify the bug ? On 28/08/2019

[Chicken-users] Obscure bug with srfi-18, mailbox and coops

Thank you your awesome reactivity ! > Is this a different error, or caused by the problem you observed? I don't really know to be honest. This is the bug I am really tracking and I don't know if it come from a logical error in the code or if it come from the other bug I described before. The

[Chicken-users] Obscure bug with srfi-18, mailbox and coops

Hello, I am currently trying to write a multi-format (JSON and msgpack) multi-transport (TCP, Unix ports, file ports) RPC server and client egg for Chicken. I have a decent architecture for my program (I think) but I currently face an inexplicable bug that randomly appear and that I cannot