Save Your Data, man!
Project powered by:
Contributing to this project:
In the tradition of Open Source projects, any and all forms of contribution and feedback
are welcomed. That includes, but is not limited to:
i am in no way averse to other coders coming in and hacking around on s11n:
the whole source tree is up for experimentation and improvement.
- Submitting new code or fixes/changes for existing code.
- Suggest changes for improvements.
- Report bugs via our SourceForge project page.
- Ask questions! These help us improve documentation.
If this project interests you, and if you would like to help keep it going, please
consider making a small donation via
SourceForge's donation system.
This project is currently funded entirely by my spare change, and any financial help would be
greatly appreciated! (As a bonus: financial contributors get utmost-priority support and get
their feature suggestions added to the lib ASAP whenever practical.)
The list of contributors just keeps on growing, and it is with great pleasure that
i list each and every one of them below. The list of contributors is
also published as an RSS feed.
And many thanks to those of who have contributed bug reports!
- Rusty "Bozo" Ballinger, conceptual forefather of s11n
Rusty's work on the classloading and serialization layers
for the QUB project
were the original inspirations for the s11n project. i wanted
that level of power in my non-Qt applications, and set out to write an STL-based equivalent...
- Bonnie and David Pickartz
My mother and stepfather made a huge donation to this project in the summer of 2004, so that i could go on working on it without
having to find a full-time job to support myself. While i did end
up going back to work in August 2004, the donation was in any case a life-saver. All users of s11n are encouraged to
pay them a visit and buy a house from them:
- Steve Madere
Steve suggesting adding unit tests to the 0.9.x tree. Within an hour of doing so, two significant bugs were found and fixed.
He also made a very generous donation via the
- Patrick Lin
First caught a long-standing compile bug brought on by a typo in some template code. He was then the first to demonstrate and help
localize a major list deserialization bug (dubbed "Patrick's Bug"),
which was fixed in 0.9.17.
- Andreas Jochens
Submitted several patches for s11n 0.9.x for compiling under gcc 3.4.
- Mike Radford
Fixed several typename problems related to moving to gcc 3.4, and allowed me ssh access to his box to fix the rest. The 1.0.1 release was made because of Mike's work.
- Tom of comp.lang.c++
Provided a clever fix for an annoying "interface bug" in the classloader library.
- Gary Boone
Gary is one of s11n's earliest adopters, contributed to the documentation, and was instrumental in spurring on the 0.7-to-0.8 rewrite.
- Roger Leigh
Roger introduced me to libltdl, allowing us to add more varied DLL loading options to s11n's classloader.
- Marshall Cline
C++ FAQ fame helped to correct documentation errors regarding cycles, graphs, and trees.
- Ton Oguara
Ton's feedback on version 0.6 was the major driver behind the 0.6-to-0.7 rearchitecting.
- Max Hofer
Max's feedback about the sucky compile times prompted a lot of experimentation to cut compile times down. The 14x increase he reported when using s11n has been cut considerably since then (summer of 2004).
- Anders Hedstroem
Anders wrote the MySQL library which is used by the mysql_serializer. He didn't write it for s11n, but he did accept some patches back into his mainstream release.
- Christian Prochnow
Project lead of the P::Classes
project, Christian allows me to port s11n into their 2.x tree,
which is a great opportunity for bug-finding and cleanups.
- Gregor Jehle
Gregor reported compile problems on AMD64 platforms and allowed me ssh access to his box to fix them. Unfortunately, his box was so fast that 50k of error text would fly by before Ctrl-C would respond over my 56k modem line ;).
- martin f. "madduck" krafft
martin is a continuing feedbacker on libs11n and the software developed around this project. His ability to always come up with a strong flip-side argument for nearly any proposal always gives me new things to think about. He originally came aboard during an attempt to get 0.8.x into the Debian tree.
- Meyers, Alexandrescu, Sutter, and Josuttis
No, of course these demi-gods didn't contribute directly, but their collective works have been instrumental in developing s11n:
Modern C++ Design
is essential reading for fans of C++ templates.
Meyers' "Effective" series is always good for practical day-to-day guidance.
Josuttis' "C++ Templates" was instrumental in learning enough
about template specializations to write s11n the way i wanted to.
Herb Sutter's "What's in a Class?" article caused me to rethink
and rewrite lots of s11n's early code.
- Fabio Picciani
Fabio contributed the "fred" mascot which sometimes appears
on the s11n site. Need a flamboyant Italian with a strong
sense of Fashion and a good eye for colors? Visit
sat down with me and ported s11n 1.1.2 to Windows, using XP and MS Dev Studio 2003 and 2005 Beta 1. This is a major milestone for the project.
- Pete Harlow
Pete Harlow did an absolutely amazing job of porting the 1.2.x library manual from Lyx to OpenDocument Format (ODF). The plan is to use ODF as the master document format going forward.
Rattlemouse, from Russia, reported a memory leak in 1.2.2, leading to two important fixes in 1.2.3 and the (re)addition of unit tests to the source tree.
- James Ingraham
James provided two fixes for building s11n on QNX with gcc 3.3.x.
- Jason Kottler
First reported the problem of serializing uchars as full-fledged objects, which could cause control characters to end up in output files, making them unreadable.
- Damien Hocking
Was the first to report s11n working as a DLL on Windows platforms, and he contributed the patches needed for it.
- Ryan Fogerty
Was the first to report a portability problem in the lex-based code when upgrading to gcc 4.4, and sent patches for it. He's the reason 1.2.10 got released.
- Yuchen Xie
Contributed the ebuild file for Gentoo systems.
If i have inadvertently left you off of this list, please
send me a mail
and i will happily correct the ommission as soon as possible.