To start, I think the documentation would benefit from a concise description of the problem you're trying to solve and how you propose to solve it--in plain language, of course. Perhaps a few examples of serialization common in other languages would be appropriate, as you're trying to fix a problem in C for which many languages have intrinsic or at least commonly accepted solutions. As part of that, you might compare and contrast serialization and persistence as implemented in COM, Corba, or Java.
I have to agree with some of the past comments on the library: the names of the macros are quite confusing. If you must use abbreviations, I would use the accepted (or de facto standard) English abbreviations, e.g. "ser" for serial and serialize and "ptr" for pointer. That's still making an assumption about your audience, though. You may choose to use abbreviations accepted by the computer science community or some other group of programmers. In any case, after skimming the document, it's not at all clear to me what each macro does. Perhaps it should be? That could also indicate a lack of knowledge on my part, so that particular comment may not hold any weight. ;-)
Are the library and serialized objects portable? i.e. Can I serialize an object on a big-endian system and deserialize the output on a little-endian system without corrupting data? How about interoperability with other serialization schemes?
Have you looked at tpl <
http://tpl.sourceforge.net/>? (I imagine it's pronounced tuple, but I can't confirm that.) Many of the concepts appear similar to yours. Perhaps your project could add value to tpl or vice versa.
Trev
