Re: [PATCH] Clean up some hacks and obsolete code

> On May 21, 2020, at 5:44 AM, Peter Bex wrote: > > More interestingly, it seems that define-record-printer either doesn't > even work, or we're using it wrong somehow: > > No clue why this doesn't work. I checked, in CHICKEN 4 this worked, > so I think we broke this somewhere during our

Re: [Chicken-hackers] [PATCH] Re: Alternative egg installation directories

> On Jun 18, 2017, at 3:35 PM, Mario Domenech Goulart > wrote: > > On Sun, 28 May 2017 23:22:40 +0200 felix.winkelm...@bevuta.com wrote: > >> Here a patch for this. CHICKEN_INSTALL_PREFIX overrides the bin, >> include or share directories when generating the install scripts. Note >> that the

[Chicken-hackers] Proposed patch for destination egg property

Hi folks,When porting chickadee to Chicken 5, I hit a roadblock when installing data files into a namespaced directory — /share/chicken/chickadee. In Chicken 4, we can execute code in .setup to obtain this directory — (make-pathname (chicken-home) "chickadee”) — and use copy-file. In Chicken 5, we

Re: [Chicken-hackers] read/write invariance of #!

> On Jan 13, 2019, at 2:16 PM, Evan Hanson wrote: > > > I don't think this change fixes the example you gave as a "certain > strange combination" in ticket #1572, i.e. (#! (foo bar)). ISTM that > happens because any whitespace after a "#!" token causes the reader to > skip everything until the

Re: [Chicken-hackers] read/write invariance of #!

> On Jan 11, 2019, at 9:47 PM, Jim Ursetto wrote: > >> On Jan 11, 2019, at 3:12 PM, Evan Hanson > <mailto:ev...@foldling.org>> wrote: >> >> In case someone decides to apply this patch, there's an unnecessary (and ...) >> around the conditional

Re: [Chicken-hackers] read/write invariance of #!

> On Jan 11, 2019, at 3:12 PM, Evan Hanson wrote: > > On 2018-12-27 10:38, Jim Ursetto wrote: >> Thanks Felix. This looks good but I haven’t had a chance to test it yet. >> Will report back. > > Any luck? This looks OK to me. > > In case someone dec

Re: [Chicken-hackers] read/write invariance of #!

Thanks Felix. This looks good but I haven’t had a chance to test it yet. Will report back. Jim > On Dec 23, 2018, at 1:46 PM, felix.winkelm...@bevuta.com wrote: > > Hi! > > Attached is a patch that seems to work for me. I don't think #!eof > should be handled specially, as it is a distinct

[Chicken-hackers] read/write invariance of #!

In Chicken 5, read/write invariance of symbols beginning with #! is violated. > (with-input-from-string (with-output-to-string (lambda () (write (string->symbol "#!abc" read) Error: invalid `#!' token: “abc" > (with-input-from-string (with-output-to-string (lambda () (write

Re: [Chicken-hackers] [C5] About `random` and its future

You could use random-bsd as a drop-in replacement if you want. http://api.call-cc.org/doc/random-bsd > On Sep 17, 2017, at 12:43 PM, lemonboy wrote: > > Hello hackers, > this time there's no patch and no code involved. I recently had some code that > used the

Re: [Chicken-hackers] Add branch prediction for C_demand checks [was: Re: [PATCH] Statically determine if argvector can be reused]

This seems to have changed somewhere between kernel 2.4.37 and 2.6.12, where it used to be: #define likely(x) __builtin_expect((x),1) #define unlikely(x) __builtin_expect((x),0) but I can’t find the exact reason it was changed. Speculating, I would guess it was changed for the 1

Re: [Chicken-hackers] [PATCH] On OS X, ensure DYLD_LIBRARY_PATH is passed to children (#1277)

Here is a patch which uses the env idea. It is a much less invasive change and might slot into 4.11. Tested only on OS X 10.11. From 412434ba807f417000620286a23141076ec6dc09 Mon Sep 17 00:00:00 2001 From: Jim Ursetto <zbignie...@gmail.com> Date: Fri, 15 Apr 2016 22:44:48 -0500 Subject:

Re: [Chicken-hackers] [PATCH] #1277 make check failure on OS X 10.11

> On Apr 15, 2016, at 18:46, felix.winkelm...@bevuta.com wrote: > > Another dirty solution would be to add a hack to those tools that invoke > uninstalled > programs via system(3) to invoke "env DYLD_LIBRARY_PATH=... " > instead. > In limited testing the env approach seems to work. But, I

Re: [Chicken-hackers] [PATCH] #1277 make check failure on OS X 10.11

Already found a bug in the Windows code of course. This patch replaces the setup-api 0003 patch from the last message. I will try to get a Windows VM running so I can test this myself. On Thu, Apr 14, 2016 at 3:22 PM, Jim Ursetto <zbignie...@gmail.com> wrote: > This is an initial

[Chicken-hackers] [PATCH] Fix typo in library path used in deployment tests

This doesn't seem to affect the results of the test, but it does quell an invalid path error in the linker. Without it a message such as ld: warning: directory not found for option '-L/Users/jim/scheme/chicken-core/tests..' will be received during the rev-app deployment test.

Re: [Chicken-hackers] [PATCH] mutex-lock! sometimes not srfi-18 compliant

Use git commit --amend to fix if you haven't committed the second one yet. Use git rebase -i to squash existing commits together. > On Nov 23, 2015, at 13:45, Jörg F. Wittenberger > wrote: > > Sorry, > > this patch needs a patch. > > Looks like I shot myself

Re: [Chicken-hackers] Cannot install regex with Chicken 4.9.1

Just a thought, weird stuff like this sometimes occurs when one version of chicken is installed in a nonstandard location and the other is installed in the standard system location, and the local one picks up the wrong libraries. Try removing the system package? On Jan 24, 2015, at 12:18,

Re: [Chicken-hackers] [PATCH] Fix #1079 by ripping out pathname expansion and putting it into an egg [Was: Re: [PATCH] add pathname-expand]

Thanks Peter! Does this egg work with older Chicken versions? I.e. can I safely replace ##sys#expand-home-path in sql-de-lite with pathname-expand across the board? Jim On Jun 22, 2014, at 6:43, Peter Bex peter@xs4all.nl wrote: On Wed, Nov 13, 2013 at 01:05:55PM +, Mario Domenech

Re: [Chicken-hackers] [PATCH] Fix #1079 by ripping out pathname expansion and putting it into an egg [Was: Re: [PATCH] add pathname-expand]

-0500, Jim Ursetto wrote: Thanks Peter! Does this egg work with older Chicken versions? I.e. can I safely replace ##sys#expand-home-path in sql-de-lite with pathname-expand across the board? Jim That should work just fine. Because the algorithm is slightly different, results may vary a bit

Re: [Chicken-hackers] pathname expansion removed from sql-de-lite open-database

, Jul 07, 2014 at 11:43:20AM -0500, Jim Ursetto wrote: Thanks Peter! Does this egg work with older Chicken versions? I.e. can I safely replace ##sys#expand-home-path in sql-de-lite with pathname-expand across the board? Jim That should work just fine. Because the algorithm is slightly

Re: [Chicken-hackers] Bug in socket egg read-line, fix diff attached

Thanks for the patch. Another user reported this same issue, but I haven't gotten a chance to look at it yet. Actually, it appears ##sys#scan-buffer-line may have changed its signature recently to return multiple values. I still need to verify that and if so, make sure the code works with

Re: [Chicken-hackers] [PATCH] fix Mac OS X build

Patches apply and build on OS X 10.9. Applied. I forgot to sign off beforehand. Jim On Jan 28, 2014, at 5:31 AM, Felix Winkelmann felix.winkelm...@bevuta.com wrote: Hello! The attached patches try to fix a few problems with building CHICKEN on Mac OS X. First, the build-tools are

Re: [Chicken-hackers] [PATCH] Remove -no-cpp-precomp flag for OS X

Builds for me, applied. FYI, this patch was encoded in iso-8859-1, and had to be converted to UTF-8 to match the Acknowledgements file. Jim On Jan 30, 2014, at 2:35 PM, Peter Bex peter@xs4all.nl wrote: Hi all, This was reported off-list: on OS X, we pass the -no-cpp-precomp option to

Re: [Chicken-hackers] [PATCH] fix Mac OS X build

On Jan 29, 2014, at 2:33 AM, Felix Winkelmann felix.winkelm...@bevuta.com wrote: From: .alyn.post. alyn.p...@lodockikumazvati.org I agree with Jim here. I don't use Xcode, but need gcc/clang for brew, chicken, c. I benefit from this project: http://kennethreitz.org/xcode-gcc-and-homebrew/,

Re: [Chicken-hackers] [PATCH] fix Mac OS X build

to run, I can't remember. Jim On Jan 28, 2014, at 1:03 PM, Felix Winkelmann felix.winkelm...@bevuta.com wrote: From: Jim Ursetto zbignie...@gmail.com Subject: Re: [Chicken-hackers] [PATCH] fix Mac OS X build Date: Tue, 28 Jan 2014 12:02:42 -0600 For the path -- actually, the build tools

Re: [Chicken-hackers] [PATCH] fix Mac OS X build

On Jan 28, 2014, at 1:53 PM, Felix Winkelmann felix.winkelm...@bevuta.com wrote: From: Jim Ursetto zbignie...@gmail.com Subject: Re: [Chicken-hackers] [PATCH] fix Mac OS X build Date: Tue, 28 Jan 2014 13:10:53 -0600 Do you mean, why isn't it in the README for Chicken? Yes, that's what

Re: [Chicken-hackers] [PATCH] fix Mac OS X build

: On 28/01/14 13:58 -0600, Jim Ursetto wrote: On Jan 28, 2014, at 1:53 PM, Felix Winkelmann felix.winkelm...@bevuta.com wrote: From: Jim Ursetto zbignie...@gmail.com Subject: Re: [Chicken-hackers] [PATCH] fix Mac OS X build Date: Tue, 28 Jan 2014 13:10:53 -0600 Do you mean, why isn't

Re: [Chicken-hackers] [PATCH] fix Mac OS X build

On Jan 28, 2014, at 3:56 PM, Felix Winkelmann felix.winkelm...@bevuta.com wrote: I don't see why not. chicken should be using /usr/bin as its binary directory, and so when xcode-select changes the install location, it will still work. (I think the shims just look up the actual XCode

Re: [Chicken-hackers] [PATCH] Fix #765 and a small can of worms related to error handling under Windows

I do have an XP install somewhere -- how do I verify the fix? (Other than making sure it compiles cleanly.) On Nov 23, 2013, at 11:06, Peter Bex peter@xs4all.nl wrote: On Fri, Nov 22, 2013 at 09:05:54PM -0600, Jim Ursetto wrote: Can you confirm it works under XP as well? If so I'll

Re: [Chicken-hackers] [PATCH] Fix #765 and a small can of worms related to error handling under Windows

Can you confirm it works under XP as well? If so I'll apply it to stability. Jim On Nov 22, 2013, at 2:43 PM, Peter Bex peter@xs4all.nl wrote: Hi all, See the attached patch, it kind of speaks for itself. I don't know why, but looks like Win7 doesn't allow cloning a handle from the

Re: [Chicken-hackers] [PATCH] Fix nonblocking socket behaviour on Windows

On Nov 20, 2013, at 4:20 PM, Peter Bex peter@xs4all.nl wrote: Hi all, Due to Shanmuhanathan's report I looked into Spiffy on Windows, and found out that multithreaded socket handling is completely broken there. Sockets are marked as nonblocking in tcp.scm, but that's done through

Re: [Chicken-hackers] [PATCH] Use noreturn attribute in clang versions which support it

On Oct 21, 2013, at 15:27, Peter Bex peter@xs4all.nl wrote: Hi all, Here's another small patch which will properly enable C_noret for clang. Currently it expands to nothing and causes a slew of warnings mostly because it doesn't understand that barf() won't return when it detects an

Re: [Chicken-hackers] [Chicken-janitors] #1045: [panic] out of memory - heap full while resizing - execution terminated (awful-picman)

Yes, an access to freed memory leading (possibly) to segfault. Let me know if you see a difference. On Oct 18, 2013, at 8:37, Alaric Snell-Pym ala...@snell-pym.org.uk wrote: On 17/10/13 23:28, Chicken Trac wrote: As discovered by Felix, it turned out to be an issue with sql-de-lite,

Re: [Chicken-hackers] [PATCH] Fix list-queue data corruption issue

On Oct 2, 2013, at 19:41, Mario Domenech Goulart mario.goul...@gmail.com wrote: On Wed, 2 Oct 2013 23:42:47 +0200 Peter Bex peter@xs4all.nl wrote: Our beloved paranoid CHICKEN has found the root cause of another long-standing and hard to debug problem: the bug in the channel egg:

Re: [Chicken-hackers] [PATCH] use -headerpad_max_install_names on Mac OS X when linking shared libs

I normally do this in CSC_OPTIONS because it's in the makefile for the compiler but it isn't transmitted to chicken-install. I think it is ok to hardcode it in csc.scm (I use -headerpad 128). Only thing I'm not sure about offhand is whether the max_install_names variant is available on all OS

Re: [Chicken-hackers] [PATCH] Fix tmpdir handling in chicken-install (#1048)

Looks good, pushed. On Aug 26, 2013, at 9:16 AM, Peter Bex peter@xs4all.nl wrote: Hi all, As Ivan reported in #1048, chicken-install's handling of TMPDIR is currently rather broken. I noticed it has a nasty hack of dealing with current-directory as if it were a parameter (which it

Re: [Chicken-hackers] [PATCH] Simplify and correct C_SIXTY_FOUR check (fix #979)

On Aug 17, 2013, at 2:36 PM, Peter Bex peter@xs4all.nl wrote: I've tested this change on NetBSD/amd64 with GCC and LLVM/Clang, and on Linux/i386 with GCC. I'd appreciate it if people on other platforms/compilers (especially Windows and OS X) could test this. Works fine on 64-bit Mac OS X

Re: [Chicken-hackers] [ANN]: Port Chicken to AIX

On Aug 13, 2013, at 7:13 AM, Mario Domenech Goulart mario.goul...@gmail.com wrote: On Mon, 12 Aug 2013 22:42:22 -0600 Erik Falor ewfa...@gmail.com wrote: Yes - the AIX sys/socket.h header file doesn't like being passed an unsigned int in the third argument. I took a cue from the call to

[Chicken-hackers] [PATCH] dynamic trace buffer resizing

Proposed patch to allow user to resize trace buffer at runtime, not just through command line option. Thoughts? 0001-Make-trace-buffer-resizable-at-runtime-via-sys-resiz.patch Description: Binary data ___ Chicken-hackers mailing list

Re: [Chicken-hackers] [PATCH] dynamic trace buffer resizing

On Aug 12, 2013, at 2:11 PM, Peter Bex peter@xs4all.nl wrote: Looks useful. Could it perhaps be more useful to make the argument to C_resize_trace_buffer a regular size_t instead of a Scheme fixnum? That might make it slightly more usable from an embedded situation. Sure -- but

Re: [Chicken-hackers] [PATCH] Add detection for hitting rest argument count limit on direct procedure application (for #910, sort-of)

Although this patch looks good and tests out fine, during the tests, chicken bloats to 1GB and gcc to 500MB, and they take forever to build apply-test -- probably because the .c file is 40MB! I'm not sure it's wise to apply as-is; it may kill some machines. Suggestions? Jim On Jul 24, 2013,

Re: [Chicken-hackers] [PATCH] Apply the same naming scheme for .so libs in libs target

Hi, This patch turned out to break the OS X build. It removes the need to set SONAME_VERSION when calling the install-bin target, and therefore implicitly sets SONAME_VERSION to .$BINARYVERSION. Unfortunately, some platforms such as OS X didn't use an SONAME_VERSION at all. It worked before

Re: [Chicken-hackers] [Chicken-users] [PATCH] Make library tests compare numbers within epsilon

I am curious why this happens though. The only thing I could think of was the number is being constant folded in one case or being computed in one case via a hardware intrinsic instead of libm in the other, but the generated C code looks identical in both cases. Perhaps some previous register

Re: [Chicken-hackers] [Chicken-users] [PATCH] Make library tests compare numbers within epsilon

On May 29, 2013, at 3:53 PM, Peter Bex peter@xs4all.nl wrote: The fpsin expands to a C inline call to sin(), whereas the sin() call expands to a call to C_a_i_flonum_sin, which is not inlineable so it has to issue a proper function call. This then goes through libm, which is potentially

Re: [Chicken-hackers] [PATCH] Fix for #1014 and minor cleanup of posix{win, unix} implementations

On May 25, 2013, at 4:46 AM, Peter Bex peter@xs4all.nl wrote: There are also some memsets still left in the code after your patch, so some get initialized using C_tm_init, and some using memset. Only strptime gets initialized with C_tm_init, and the rest with memset. strptime produces a

Re: [Chicken-hackers] [PATCH] Fix for #1014 and minor cleanup of posix{win, unix} implementations

OK, I didn't see this because it wasn't attached to the ticket. I posted an alternate patch on #1014 which just addresses the old data problem in string-time. As far as I can tell, the various uses of C_tm can not interfere with each other and all one needs to do is initialize C_tm to a sane

Re: [Chicken-hackers] windows paths with spaces

I'm reluctant to apply this patch for two reasons. 1) (compile-file) still does manual quoting on mingw32 (see the crapshell variable) and I'm not convinced this is correct with the quoting change in (qs). 2) The API docs for (qs) explicitly state that it escapes metacharacters with backslash

Re: [Chicken-hackers] Fix solaris9 build for missing trunc, round, isinf math functions

On Apr 20, 2013, at 4:45 PM, Felix wrote: From: Christian Kellermann ck...@pestilenz.org No, published patches are better not changed as they would require either a merge by everyone that already has the old patch, or you would force everyone to throw away that patch and take the other. I

Re: [Chicken-hackers] -block doesn't work for me

I thought -block precludes the use of identifiers from outside the compilation unit. On Apr 10, 2013, at 4:04 PM, Jörg F. Wittenberger wrote: Sorry, I'd had sent this to chicken-users - but I'm kinda sure those who could answer don't read that list ;-) find attache two trivial module files

Re: [Chicken-hackers] [PATCH] Restore row and column counting for ports (fixes #978)

On Mar 28, 2013, at 3:48 AM, Moritz Heidkamp wrote: Jim Ursetto zbignie...@gmail.com writes: Unfortunately, I think it is essentially impossible at this time to have the compiler do this automatically via type analysis. I believe it is possible to get the compiler to treat string ports

Re: [Chicken-hackers] [PATCH] Restore row and column counting for ports (fixes #978)

On Feb 16, 2013, at 2:14 PM, Jim Ursetto wrote: On Feb 16, 2013, at 8:54, Peter Bex peter@xs4all.nl wrote: Just removing the port position bookkeeping altogether is better, I think. I haven't done any benchmarks but Chicken's notoriously awful I/O performance might partially be due

Re: [Chicken-hackers] [PATCH 3/4] Remove ##sys#expand-home-path.

The following eggs in SVN use ##sys#expand-home-path, since this functionality is useful but was never exported as an official API: openssl osxattr posix-extras sql-de-lite sqlite3 vfs To be fair, three of those are mine. Jim On Mar 19, 2013, at 8:48 PM, Mario Domenech Goulart wrote: Hi

Re: [Chicken-hackers] [PATCH] non-termination with (declare (inline ...))

On Mar 18, 2013, at 11:22 AM, Felix wrote: From: Jim Ursetto zbignie...@gmail.com Subject: Re: [Chicken-hackers] [PATCH] non-termination with (declare (inline ...)) Date: Mon, 18 Mar 2013 10:57:49 -0500 Is that just for declare or does it also apply to define-inline? No, define-inline

[Chicken-hackers] [PATCH] Avoid context switch during TCP errno reporting

apply a different fix on top of it. Jim From d856649a414b31e50e1b4971ce1c47f693161390 Mon Sep 17 00:00:00 2001 From: Jim Ursetto zbignie...@gmail.com Date: Mon, 18 Mar 2013 13:40:05 -0500 Subject: [PATCH] Avoid context switch during TCP errno reporting There is currently the potential

Re: [Chicken-hackers] [PATCH] Avoid context switch during TCP errno reporting

On Mar 18, 2013, at 4:17 PM, Felix wrote: From: Jim Ursetto zbignie...@gmail.com Here's a full patch to avoid context switches screwing up the error message reported to the user, and also consolidates much of the error handling. Applied. Thanks. Argh! I made an error in the patch. I've

Re: [Chicken-hackers] [PATCH 1/2] tcp: disable interrupts

On Mar 17, 2013, at 1:58 AM, Florian Zumbiehl wrote: If you cannot be sufficiently sure that your approach is correct to be willing to build a full fix on it without testing first, I would consider that a sign that the approach is too fragile to rely on, at least without a good reason. I

Re: [Chicken-hackers] [PATCH] Ensure sleep seconds is a fixnum on Windows; also, don't halve sleep time

If this patch was acceptable, could someone please apply it? Thanks. Jim On Feb 19, 2013, at 9:45 AM, Jim Ursetto wrote: No, it returns 0 to indicate that zero seconds of sleep time remain (it was not interrupted), just like posix sleep. See the UNIX code, the Windows code prior

Re: [Chicken-hackers] [PATCH] fix setup-proxy to accept http URIs

Pushed. On Mar 16, 2013, at 12:43 PM, Peter Bex wrote: On Sat, Mar 16, 2013 at 12:29:35PM +0100, Michele La Monaca wrote: Oddly and inconveniently enough, (setup-proxy uri) does not not accept well-formed URIs: http_proxy=http://IP:PORT (it accepts only the short form

Re: [Chicken-hackers] [PATCH] alist-update: don't segfault on non-list

: (alist-update! 'foo 'bar '((a . b) 3 (c . d)) (cut equal? )) On Mar 16, 2013, at 3:16 PM, Christian Kellermann wrote: * Jim Ursetto zbignie...@gmail.com [130314 08:13]: Nice catch. Actually, it might be better rewritten with (##sys#check-list lst 'alist-update), although

Re: [Chicken-hackers] [PATCH 3/4] Remove ##sys#expand-home-path.

On Mar 15, 2013, at 1:04 AM, Florian Zumbiehl wrote: Remove ##sys#expand-home-path as shell expansion has no place in a filesystem API. Definitely not happening. ;) Jim ___ Chicken-hackers mailing list Chicken-hackers@nongnu.org

Re: [Chicken-hackers] [PATCH 3/4] Remove ##sys#expand-home-path.

On Mar 15, 2013, at 2:21 AM, Felix wrote: From: Florian Zumbiehl fl...@florz.de Subject: Re: [Chicken-hackers] [PATCH 3/4] Remove ##sys#expand-home-path. Date: Fri, 15 Mar 2013 07:58:02 +0100 Remove ##sys#expand-home-path as shell expansion has no place in a filesystem API. Can't we

Re: [Chicken-hackers] [PATCH 3/4] Remove ##sys#expand-home-path.

On Mar 15, 2013, at 2:21 AM, Felix wrote: From: Florian Zumbiehl fl...@florz.de Subject: Re: [Chicken-hackers] [PATCH 3/4] Remove ##sys#expand-home-path. Date: Fri, 15 Mar 2013 07:58:02 +0100 Remove ##sys#expand-home-path as shell expansion has no place in a filesystem API. Can't we

Re: [Chicken-hackers] [PATCH 3/4] Remove ##sys#expand-home-path.

On Mar 15, 2013, at 3:35 PM, Peter Bex wrote: Finally, a flag would also need to go everywhere a path is accessed (including file-open, directory, directory?, call-with-input-file, etc...) unless you make it a parameter (which would be slower, if I'm not mistaken). Oops, I see you already

Re: [Chicken-hackers] [PATCH 2/4] csi: fix untrusted code execution by (load)ing ./.csirc

On Mar 15, 2013, at 5:47 AM, Peter Bex wrote: I nominate this patch for inclusion into the stability branch. I hesitate to add it only because someone may be relying on this behavior, and not know they have to update ~/.csirc. Jim ___

Re: [Chicken-hackers] [PATCH] alist-update: don't segfault on non-list

Nice catch. Actually, it might be better rewritten with (##sys#check-list lst 'alist-update), although that is not that important. Related, alist-update! behaves weird but doesn't crash on non-alists: (alist-update! 'foo 'bar 3) ;= ((foo . bar) . 3) And it's inconsistent when you give it a

[Chicken-hackers] [PATCH] test for r/w invariance

I'd like to cherry-pick the following patch from stability into core. This would add a test for commit 863a28e3c26f2b665dcaf75d892fcb09f62c09a1 (escape single backslash in symbols when printing). Thoughts? commit a09308b04128cecf5b93564599cbedd5e564cafd Author: Jim Ursetto zbignie

Re: [Chicken-hackers] [PATCH] Fix for poll() special values in revent

On Feb 26, 2013, at 12:02 PM, Peter Bex wrote: Hi all, Here's a patch to deal with special situations in poll(). Mario found a problem on Linux: [...] In any case, we don't check poll() revents for any other values than POLLIN/POLLOUT, which is clearly wrong; if a pipe is closed, there's

[Chicken-hackers] [PATCH] Ensure sleep seconds is a fixnum on Windows; also, don't halve sleep time

sleep accepts any type arg but should accept only fixnums; also fix a regression in be44f5328. 0001-Ensure-sleep-seconds-is-a-fixnum-on-Windows-also-don.patch Description: Binary data ___ Chicken-hackers mailing list Chicken-hackers@nongnu.org

Re: [Chicken-hackers] [PATCH] Ensure sleep seconds is a fixnum on Windows; also, don't halve sleep time

, 2013 at 02:03:44AM -0600, Jim Ursetto wrote: sleep accepts any type arg but should accept only fixnums; also fix a regression in be44f5328. Shouldn't it return undefined rather than 0? This seems like a bug in the original implementation. Cheers, Peter -- http://www.more-magic.net

Re: [Chicken-hackers] [PATCH] Restore row and column counting for ports (fixes #978)

On Feb 16, 2013, at 8:54, Peter Bex peter@xs4all.nl wrote: Just removing the port position bookkeeping altogether is better, I think. I haven't done any benchmarks but Chicken's notoriously awful I/O performance might partially be due to the port position bookkeeping. I seriously doubt

Re: [Chicken-hackers] [PATCH] do not apply PROGRAM_PREFIX/PROGRAM_SUFFIX to target include directory in a cross-chicken build

I can't test the functionality but as long as it doesn't break existing builds I will apply it to stability. OK? On Feb 9, 2013, at 5:50, Mario Domenech Goulart mario.goul...@gmail.com wrote: Hi, On Thu, 7 Feb 2013 13:11:28 +0100 Christian Kellermann ck...@pestilenz.org wrote: * felix

Re: [Chicken-hackers] [PATCH] A cache system for the build environment

On Feb 4, 2013, at 1:43 PM, Michele La Monaca wrote: The goal of this patch is to cache build-related variables to avoid to repeat them in every single make invocation after the first one. [...] For example: make PREFIX=/tmp/chicken ARCH=x86-64 vi file_to_be_fixed make make install

Re: [Chicken-hackers] substring function and bounds checks

On Feb 5, 2013, at 5:55 PM, Michele La Monaca wrote: What I can say... Well, maybe one day I will see the light, in the meanwhile I would just have preferred a more useful substring function. I really think that the one provided by chicken is simply not on par with other languages, sorry.

Re: [Chicken-hackers] substring function and bounds checks

On Feb 5, 2013, at 4:11 PM, Michele La Monaca wrote: Maybe this is not the right list for that, sorry. But is there a good reason for this [error on out-of-bounds substring access] behavior? I think it's along the lines of (cdr '()) being an error in Scheme instead of NIL as in Lisp. Jim

Re: [Chicken-hackers] [PATCH] Fix for #568

On Feb 3, 2013, at 2:05 PM, Peter Bex wrote: On Sun, Feb 03, 2013 at 12:00:42PM -0800, Kon Lovett wrote: On Feb 3, 2013, at 11:50 AM, Peter Bex peter@xs4all.nl wrote: That reminds me: in posixunix.scm the read-line code sets some slot number 5. I was unable to figure out what this was

Re: [Chicken-hackers] [PATCH] Fix for #568

Gotcha. I was using read-char exclusively. I imagine that read-line should zero out the column, at least. That shouldn't be hard. On Feb 3, 2013, at 14:58, Peter Bex peter@xs4all.nl wrote: On Sun, Feb 03, 2013 at 02:54:04PM -0600, Jim Ursetto wrote: On Feb 3, 2013, at 2:05 PM, Peter Bex

[Chicken-hackers] [PATCH] Make heap_size size_t instead of uint, permitting 4GB heap on 64-bit systems (#974)

Fixes Arthur Maciel's crash/hang with large datasets. This should also go in stability/4.8.0 in my opinion. 0001-Make-heap_size-size_t-instead-of-uint-permitting-4GB.patch Description: Binary data ___ Chicken-hackers mailing list

Re: [Chicken-hackers] [PATCH] A native scheme install

On Jan 29, 2013, at 9:35 AM, Peter Bex wrote: On Tue, Jan 29, 2013 at 04:15:13PM +0100, Michele La Monaca wrote: Doesn't this create a bootstrapping problem while installing Chicken? Chicken needs a working install to install the runtime system, but your install needs the runtime system to be

Re: [Chicken-hackers] [PATCH] A native scheme install

On Jan 29, 2013, at 11:20 AM, Michele La Monaca wrote: Anyway, you can always fall back to a different install program if needed. Just set INSTALL_PROGRAM to your favorite install command. Which is why the existing solution works fine. No need to patch Makefiles to try. Just:

Re: [Chicken-hackers] [PATCH] A native scheme install

On Jan 29, 2013, at 12:55 PM, Michele La Monaca wrote: Ehi, I am not saying let's switch to install.scm as the default installer (not for now at least). My proposition is: let's bundle install.scm in the tarball and let's give the user an extra chance to have a BSD-compatible install program.

Re: [Chicken-hackers] Warnings building on Solaris/suncc

On Jan 29, 2013, at 1:00 PM, Peter Bex wrote: Attached is a patch against master fixing both issues. I've fixed the calls to C_save_and_reclaim in the same way calls to C_reclaim had already been fixed: a straight up cast to (void *). It feels a little shady, but it should work. I don't

Re: [Chicken-hackers] [PATCH] A native scheme install

If you can demonstrate that some core code (such as chicken-install) would be improved with the addition of file-install then it might be worth adding to core (probably in setup-api though). I still think putting the file-install code in install.scm is a better solution for that particular script

Re: [Chicken-hackers] [PATCH] use test -f instead of test -e (#965)

Pushed. On Jan 21, 2013, at 2:13 PM, Felix wrote: A change needed for Solaris. Reported by Mikele. cheers, felix From 7dbc4bbd71badd8f71107304f5789bde015c43ee Mon Sep 17 00:00:00 2001 From: felix fe...@call-with-current-continuation.org Date: Mon, 21 Jan 2013 21:11:02 +0100 Subject:

[Chicken-hackers] stability/4.8.0 test release available

I've uploaded a test distribution tarball of stability/4.8.0 [1]. This should contain everything that will go into 4.8.0.1 unless we find a problem. If anyone would like to test it, it would be appreciated. I also pushed the patches to the throw-away tmp/stability/4.8.0 branch [2] in my

Re: [Chicken-hackers] Updating stability...

I've backported and/or applied these to my tree, with the exception of these so far: # c2ea63b (uint64 fix) depends on 09bfacd1 (Windows 64 bit patch) c2ea63b340995b1882d9ed400db0019c1686aa11 # 67ca64e (clang warnings) depends on 09bf6acd1 (Windows 64 bit patch)

Re: [Chicken-hackers] [PATCH] Simple fix to get rid of the openbsd linker warnings (#923)

Also prevents the clang warnings on OS X from causing a failing test. On Sep 14, 2012, at 3:58 AM, Peter Bex wrote: Hi all, I think this trivial patch could make it into the release. This runs the scrutiny tests only in analysis mode. We don't need to generate C code and we certainly

[Chicken-hackers] [PATCH] Re: OS X: clang's failing 'make check' w/ 4.8.0rc3 tarball

This patch trivally silences the errors (also see #917). 0001-Silence-clang-return-type-warnings-by-removing-else-.patch Description: Binary data On Sep 9, 2012, at 5:21 PM, Derrell Piper wrote: Peter, Hum, okay. Let me attach the complete log just to be clear... Thanks, Derrell

Re: [Chicken-hackers] [PATCH] chicken.h: define C_noret as __attribute__ ((noreturn)) for clang too

As mentioned in #917, that conditional is in there deliberately because the clang build was observed to break with it in. Felix added it originally when he was building with an ancient clang. When I was getting clang working again, I left it alone because I still saw breakage (or at least it was

Re: [Chicken-hackers] [PATCH] deep-stack option, declaration and build-mode

On Aug 1, 2012, at 7:07 AM, Felix wrote: Enabling this mode by default should IMHO be avoided, since runaway recursions (which is the usual reason for stack-exhaustion) will consume all available memory and thus may bring the machine to a halt. I think it will hit the stack ulimit (probably

Re: [Chicken-hackers] [PATCH] deep-stack option, declaration and build-mode

On Aug 1, 2012, at 1:59 PM, Jim Ursetto wrote: On Aug 1, 2012, at 7:07 AM, Felix wrote: Enabling this mode by default should IMHO be avoided, since runaway recursions (which is the usual reason for stack-exhaustion) will consume all available memory and thus may bring the machine to a halt

Re: [Chicken-hackers] tcp-shutdown

If you close the input or output port (e.g. with close-output-port) then the tcp unit will shutdown that half of the conversation. Does that not work? Jim On Jul 25, 2012, at 12:18, Seth Alves al...@hungry.com wrote: I have some code that uses the openssl egg. I'm not able to find a way

Re: [Chicken-hackers] [PATCH] limit number of live finalizers

Here's some background information from when this problem first reared its head six years ago. http://lists.gnu.org/archive/html/chicken-users/2006-01/msg00082.html Summary. Although the GC is capable of queuing only a subset of pendable finalizers (in case the pending buffer is fixed-size and

Re: [Chicken-hackers] [PATCH] catch exceptions in finalizers, remove dynamic resizing of finalizer vector

Hi Felix, On Jun 19, 2012, at 1:03 PM, Felix wrote: From: Jim Ursetto zbignie...@gmail.com Might I suggest that these nice thorough explanations be put in the patch message itself (preceded by a blank line), so we always have them at hand. Sure. Do you want one blank line or two? I can

[Chicken-hackers] [PATCH] #870: SRFI-13's string comparison procedures return integers

Attached patch fixes ticket #870. From 72b4138d0fd1f314f9129ea1bf54f67892e25d38 Mon Sep 17 00:00:00 2001 From: Jim Ursetto zbignie...@gmail.com Date: Mon, 18 Jun 2012 20:16:24 -0500 Subject: [PATCH] Ensure that srfi-13 string= and its string-comparison friends return booleans on success

Re: [Chicken-hackers] [PATCH] Change setjmp/longjmp to _setjmp/_longjmp to avoid overhead and fix signal masking bug

On Jun 13, 2012, at 7:28 PM, Mario Domenech Goulart wrote: Unfortunately I could not observe any improvement on Linux x86. The performance is actually slightly worse with your patch (using master, c48a109d668f3186bb4a213940c0b0b81a1ad03d). I run the benchmarks with no csc options and with

Re: [Chicken-hackers] [PATCH] Change setjmp/longjmp to _setjmp/_longjmp to avoid overhead and fix signal masking bug

On Jun 13, 2012, at 8:51 PM, John Cowan wrote: On Cygwin, _setjmp and _longjmp are supported. I can test, but probably not until next week. Cool, thanks. We can probably assume that if it compiles, it works fine. On Solaris, _setjmp and _longjmp don't manipulate the signal mask, whereas

Re: [Chicken-hackers] tcp-connect looses socket-fd upon timeout

Applied to master and stability, thanks. I verified the behavior manually with lsof. Note that this was only an issue if tcp-connect-timeout is set, which is not the case by default; if the OS itself times out the connection, it got properly closed. On May 16, 2012, at 10:13 AM, Jörg F.

Re: [Chicken-hackers] Patch to use better PRNG on BSD's

Currently the only reason a better PRNG is needed in core is because of the new hash table randomization stuff that is also in core (as of the upcoming Chicken 4.8). User code can use any one of the random eggs. Cryptographic quality is probably overkill. On Apr 11, 2012, at 6:21 AM, Thomas Chust

Re: [Chicken-hackers] Patch to use better PRNG on BSD's

We've been through this conversation multiple times. For example, I already proposed a patch using random -- which is way more portable than arc4random (!!) -- and it was rejected. The ultimate solution is a self-contained PRNG of reasonable quality in core. Or users may use the random-bsd egg

Re: [Chicken-hackers] Patch to use better PRNG on BSD's

E.g.: http://bugs.call-cc.org/ticket/218 On Apr 10, 2012, at 3:47 PM, Jim Ursetto wrote: We've been through this conversation multiple times. For example, I already proposed a patch using random -- which is way more portable than arc4random (!!) -- and it was rejected. The ultimate

Re: [Chicken-hackers] [PATCH] random returns the same number on x86_64 all the time

On Mar 4, 2012, at 12:42 AM, John Cowan wrote: That makes no sense when you are asking for an integer between 0 and 2^62-1. In that case the underlying interface should be asked to deliver two 32-bit values. That gets you up to 53 bits due to the (double) scaling, but the bottom bits will

  1   2   >