Re: [Chicken-hackers] On Hash Collisions (28C3)

2012-01-01 Thread Jörg F . Wittenberger
On Dec 31 2011, John Cowan wrote: Thomas Bushnell, BSG scripsit: Huh? The point is that well-chosen hash collisions can force the algorithm into its worst case behavior, and if that's linear, it's a problem. Choosing a linear algorithm to begin with is hardly a win! Let me second that one.

Re: [Chicken-hackers] On Hash Collisions (28C3)

2012-01-01 Thread Peter Bex
On Sun, Jan 01, 2012 at 01:08:39PM +0100, Jörg F. Wittenberger wrote: On Dec 31 2011, John Cowan wrote: Huh? The point is that well-chosen hash collisions can force the algorithm into its worst case behavior, and if that's linear, it's a problem. Choosing a linear algorithm to begin with is

Re: [Chicken-hackers] On Hash Collisions (28C3)

2012-01-01 Thread John Cowan
Peter Bex scripsit: Agreed. Changing datastructures is not an option. Why not? It's a matter of replacing a datastructure whose worst-case cost is quadratic with one whose worst-case cost is linear. Do we even know what the break-even point is between a-lists with their higher algorithmic

Re: [Chicken-hackers] On Hash Collisions (28C3)

2012-01-01 Thread Peter Bex
On Sun, Jan 01, 2012 at 09:57:15AM -0500, John Cowan wrote: Peter Bex scripsit: Agreed. Changing datastructures is not an option. Why not? Because not fixing hash tables makes them into another footgun. Also because fixing them transparently is simple and has almost zero overhead. It's

Re: [Chicken-hackers] On Hash Collisions (28C3)

2012-01-01 Thread John Cowan
Peter Bex scripsit: Yes, and doing it in *every* *freaking* program. Including third-party libraries written long ago or by people assuming a sane srfi-69 implementation (or more likely, not having thought about it). Not at all. Only fixing programs that are exposed to potentially malicious

Re: [Chicken-hackers] On Hash Collisions (28C3)

2012-01-01 Thread Peter Bex
On Sun, Jan 01, 2012 at 10:29:18AM -0500, John Cowan wrote: Peter Bex scripsit: Yes, and doing it in *every* *freaking* program. Including third-party libraries written long ago or by people assuming a sane srfi-69 implementation (or more likely, not having thought about it). Not at

Re: [Chicken-hackers] On Hash Collisions (28C3)

2012-01-01 Thread Alan Post
On Sun, Jan 01, 2012 at 04:36:41PM +0100, Peter Bex wrote: On Sun, Jan 01, 2012 at 10:29:18AM -0500, John Cowan wrote: Peter Bex scripsit: Yes, and doing it in *every* *freaking* program. Including third-party libraries written long ago or by people assuming a sane srfi-69

Re: [Chicken-hackers] On Hash Collisions (28C3)

2012-01-01 Thread Ivan Raikov
I also do not understand why using different data structures is not under consideration. There are many algorithms and data structures for handling collisions so that hash table access remains efficient even with a high rate of collisions. Why not have the option to choose the data structure

Re: [Chicken-hackers] ignore-repository

2012-01-01 Thread Felix
From: Jim Ursetto zbignie...@gmail.com Subject: [Chicken-hackers] ignore-repository Date: Sun, 1 Jan 2012 02:37:07 -0600 I noticed that the compiler's -ignore-repository option does (repository-path #f), but due to the implementation of repository-path (which uses #!optional) this will have