Custom Query (1630 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (34 - 36 of 1630)

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Ticket Resolution Summary Owner Reporter
#1768 fixed Wrong macro added to chicken-config.h in Makefile.cross-linux-mingw lattay
Description

Hi, I noticed that there is a mistake in Makefile.cross-linux-mingw. In the process of creating chicken-config.h, this Makefile declares HAVE_ALLOCA_H when it should declare HAVE_ALLOCA only. Here is a "patch":

diff --git a/Makefile.cross-linux-mingw b/Makefile.cross-linux-mingw
index 929e140..6d6a690 100644
--- a/Makefile.cross-linux-mingw
+++ b/Makefile.cross-linux-mingw
@@ -105,7 +105,7 @@ chicken-config.h: chicken-defaults.h
 	echo "#define HAVE_UNISTD_H 1" >>$@
 	echo "#define HAVE_UNSIGNED_LONG_LONG 1" >>$@
 	echo "#define STDC_HEADERS 1" >>$@
-	echo "#define HAVE_ALLOCA_H 1" >>$@
+	echo "#define HAVE_ALLOCA 1" >>$@
 	echo "#define HAVE_DIRECT_H 1" >>$@
 	echo "#define HAVE_ERRNO_H 1" >>$@
 	echo "#define HAVE_LOADLIBRARY 1" >>$@
#1766 duplicate patch to port the netstring egg to CHICKEN 5 Moritz Heidkamp Christopher Brannon
Description

I needed to be able to talk to something that speaks netstrings, so I ported the netstring egg to CHICKEN 5. The patch is attached.

#1765 worksforme enable-warnings time-travelling shenanigans Idiomdrottning
Description

(import miscmacros (chicken condition)) (define-syntax-rule

(bound-procedure? name) (handle-exceptions

ex

#f (procedure? name)))

(enable-warnings #f) (define wtf (bound-procedure? if)) (enable-warnings #t) wtf

;; ↑↑ quietly and politely evals to #f

(begin

(enable-warnings #f) (define wtf (bound-procedure? if))

(enable-warnings #t) wtf)

;; ↑↑ expands to a let form (which is fine of course) and complains in ;; the REPL because warnings apply retroactively to the entire form.

I've tried enabling the warnings via (let ((ret ...)) enable ret) dynamic-wind or via force/delay or via just a lambda that gets called, but no matter how I do it, it retroactively wants to print warnings.

I even did

(define (re-enable-warnings val ret)

(enable-warnings val) ret)

(re-enable-warnings #f (bound-procedure? if))

;;; politely evals to #f

(re-enable-warnings #t (bound-procedure? if))

;;; causes a ruckus

The time travelling super powers of call-with-current-continuation that the REPL uses is haunting me…!

This just can't be right!

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