Custom Query (1630 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (37 - 39 of 1630)

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
Ticket Resolution Summary Owner Reporter
#678 worksforme bug in specialized-io egg Jeronimo Pellegrini felix winkelmann
Description

The foreign code should probably be declared to return int:

(define write-one-char
  (lambda (c port)
    (if (fx= 1 ((foreign-lambda* void ((char var)
                                       (scheme-object port))
                                 "#include <stdio.h> \n"
                                 "if (fputc (var, C_port_file(port)) == EOF)"
                                 "     return(1);"
                                 "else"
                                 "     return(0);")
                c port))
        (specialized-io-error "write-one-char: failed!"))))

#696 worksforme Stock 4.7.0 chicken cannot compile current trunk johnwcowan
Description

When attempting to compile setup-api.scm, setup-download.scm, chicken-install.scm, chicken-uninstall.scm, and chicken-status.scm, my stock 4.7.0 chicken in /usr/local/bin crashes with the absurd error message:

Syntax error (import): cannot import from undefined module

        scheme

        Expansion history:

        <syntax>          (##core#begin (module setup-api ((run execute) compile standard-extension make make/proc host-extens......
        <syntax>          (module setup-api ((run execute) compile standard-extension make make/proc host-extension install-ex......
        <syntax>          (##core#module setup-api ((run execute) compile standard-extension make make/proc host-extension ins......
        <syntax>          (import scheme chicken foreign irregex utils posix ports extras data-structures srfi-1 srfi-13 files......    <--

The workaround is to recompile these files using the chicken already built in the working directory, which has no problem with them. This is after setting CSC_OPTIONS to "-I/usr/local/include/chicken", as required on Cygwin.

#707 worksforme ##sys#file-info needs to signal an error if the fstat syscall goes bad Christian Kellermann
Description

I think it is bad style to ignore the errno error signalling mechanism when doing syscalls. Bug #706 shows that this can result in serious mischief.

##sys#file-info is the first culprit that I have identified, but I suspect all runtime calls lack a error propagation mechanism.

Maybe a more general approach on how to do this is needed. At the time of writing this I am favoring raising exn i/o conditions for the exceptional cases. Also would these calls be reentrant?

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
Note: See TracQuery for help on using queries.