> I tried your code but I got all kinds of compile errors. Sorry, but it's
> gotten to be too much effort to just open a file.
Indeed, that's understandable. Sorry for not being able to help, but
we are definitely working on improving this situation for the next
major release of CHICKEN.
felix
I tried your code but I got all kinds of compile errors. Sorry, but it's
gotten to be too much effort to just open a file.
Op di 26 dec 2023 om 21:45 schreef :
> > Thanks for the responses. I tried what I could, but it still doesn't
> work.
> > I wrote some code to test if I can open and close a
> Thanks for the responses. I tried what I could, but it still doesn't work.
> I wrote some code to test if I can open and close a file. The C code works
> but the Chicken code doesn't.
>
> (import (chicken foreign))
>
> (foreign-declare "#include ")
> (foreign-declare "#include ")
>
> (define
Thanks for the responses. I tried what I could, but it still doesn't work.
I wrote some code to test if I can open and close a file. The C code works
but the Chicken code doesn't.
-- test.c --
#include
#include
// this file needs to be saved with explicit BOM (byte order mark)
On Mon, Dec 25, 2023 at 6:07 AM wrote:
> I'm not too familiar with the way Windows handles non-ASCII characters
> in operating system calls, but I assume that what gets passed to the C
> library runtime functions like fopen(3), etc. assumes a particular
> encoding.
>
Basically, there are two
> Hi everyone,
>
> I want to read input from a file that contains accented characters in its
> name, and Chicken says that it can't open the file. The source code is
> saved in a UTF-8 encoded text file.
> [...]
> I use Windows, and I run the script in the Command Prompt. Before running
> it, I
