Custom Query (1630 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (64 - 66 of 1630)

Ticket Resolution Summary Owner Reporter
#1722 fixed srfi-193: failure in tests lassik Mario Domenech Goulart
Description

Some tests fail in the test suite of srfi-193 version 0.1.1: http://salmonella-linux-x86.call-cc.org/master-debugbuild/gcc/linux/x86/2020/10/25/salmonella-report/test/srfi-193.html

All tests pass in version 0.1.

#1721 fixed include file install w/ CHICKEN_INSTALL_PREFIX causes duplicated install prefix in final pathname Kon Lovett
Description

The "After" below fixes my little problem but is not a suggested solution.

-- levenshtein.egg relevant extract:

(scheme-include levenshtein-cost

(files "levenshtein-cost-interface.types.scm"

"levenshtein-cost-interface.scm" "levenshtein-cost-number.scm" "levenshtein-cost-fixnum.scm" "levenshtein-cost-flonum.scm"))

(scheme-include levenshtein-sequence

(files "levenshtein-sequence-interface.types.scm"

"levenshtein-sequence-interface.scm" "levenshtein-sequence-vector.scm" "levenshtein-sequence-string.scm" "levenshtein-sequence-utf8.scm"))

-- Before & After

#495 $ find /usr/local -name 'levenshtein*.scm' /usr/local/chicken/5/usr/local/chicken/5/share/levenshtein-sequence-interface.types.scm /usr/local/chicken/5/usr/local/chicken/5/share/levenshtein-cost-flonum.scm /usr/local/chicken/5/usr/local/chicken/5/share/levenshtein-cost-fixnum.scm /usr/local/chicken/5/usr/local/chicken/5/share/levenshtein-sequence-vector.scm /usr/local/chicken/5/usr/local/chicken/5/share/levenshtein-sequence-string.scm /usr/local/chicken/5/usr/local/chicken/5/share/levenshtein-sequence-interface.scm /usr/local/chicken/5/usr/local/chicken/5/share/levenshtein-sequence-utf8.scm /usr/local/chicken/5/usr/local/chicken/5/share/levenshtein-cost-number.scm /usr/local/chicken/5/usr/local/chicken/5/share/levenshtein-cost-interface.scm /usr/local/chicken/5/usr/local/chicken/5/share/levenshtein-cost-interface.types.scm

#499 $ srcdiff egg-compile.scm 56,65c56 < ;returns s2 w/o any, one, leading s1 < (define (string-prefix-strip s1 s2) < (let loop ((ls1 (string->list s1)) (ls2 (string->list s2))) < (cond ((null? ls1) (list->string ls2)) < ((null? ls2) s2) < ((char=? (car ls1) (car ls2)) (loop (cdr ls1) (cdr ls2))) < (else s2)) ) ) < < (define strip-install-prefix) < (define override-prefix) ---

(define override-prefix

67,68d57 < (set! strip-install-prefix (lambda (pn) (string-prefix-strip prefix pn))) < (set! override-prefix 152c141,142 < (strip-install-prefix dest*)))))) ---

dest*)))))

#495 $ find /usr/local -name 'levenshtein*.scm' /usr/local/chicken/5/share/levenshtein-sequence-interface.types.scm /usr/local/chicken/5/share/levenshtein-cost-flonum.scm /usr/local/chicken/5/share/levenshtein-cost-fixnum.scm /usr/local/chicken/5/share/levenshtein-sequence-vector.scm /usr/local/chicken/5/share/levenshtein-sequence-string.scm /usr/local/chicken/5/share/levenshtein-sequence-interface.scm /usr/local/chicken/5/share/levenshtein-sequence-utf8.scm /usr/local/chicken/5/share/levenshtein-cost-number.scm /usr/local/chicken/5/share/levenshtein-cost-interface.scm /usr/local/chicken/5/share/levenshtein-cost-interface.types.scm

#1720 fixed r7rs "write" procedure does not escape "invalid" symbols Duy Nguyen
Description

r7rs defines an alternative way to present a symbol that's otherwise invalid identifiers, by putting it inside ||. This is implementation-specific in r5rs.

The problem can be seen with (write (features)) where 64bit is not escaped (i.e. |64bit|) while it is for all the r7rs schemes I have my hands on.

This is not a problem when within chicken because both the reader and writer are in sync. I found this out because I updated chibi-snow to read (features) from chicken. Chibi does not like '64bit' symbol without ecaping.

Note: See TracQuery for help on using queries.