> Btw, the SVN at hasn't been updated for quite a while.

It has been a while since a significant bug has been found.

> Is it still used for development

No, I do not like the code base, it is too difficult to read and modify.
The version I am working on would effectively be a re-write.
However, the development as been stalled since the Core 2 duo
introduction (branch prediction + cache interaction).  The current
Haswell processor seems to have fixed the problem.  So I am
making very good progress on the next version of Judy.

Thanks for your interest,


Doug Baskins <>

On Tuesday, November 5, 2013 2:52 AM, Antony Dovgal <> wrote:
On 2013-11-01 20:42, Doug Baskins wrote:
> Tony:
> Thank you for your contributions.  I took a brief look at your patches.  The bug
> to example code (Judy1Op()) seems so obvious, I dont understand why it took so long to
> hear about it.  The other fixes to the build need to be done, however the symlink instead
> of copy (if I remember correctly) did not work with some versions of "make".
> I would appreciate it if you would send a tar-ball of your fixed version (without symlinks)
> so I can more easily merge with my newest version of Judy.

Ok, you can download the version without symlinks patch here:

You can also download individial patches from my initial email here:

Btw, the SVN at hasn't been updated for quite a while.
Is it still used for development?

Antony Dovgal

November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register

Judy-devel mailing list