Age | Commit message (Collapse) | Author | |
---|---|---|---|
2009-08-27 | Some cleanup and reformatting, fixed the benchmarks. | Joshua Haberman | |
2009-08-24 | Significant memory-management refactoring any Python extension. | Joshua Haberman | |
2009-08-15 | A few more thread-safety fixes. | Joshua Haberman | |
2009-08-12 | Refactoring: unify upb_msg. | Joshua Haberman | |
The cost is that a upb_msg will now always have an overhead of 2*sizeof(void*). This is comparable to proto2 overhead. The benefit is that upb_msg is now self-describing, and read-only algorithms can now operate on a upb_msg regardless of the memory-management scheme. Also, upb_array and upb_string now know inherently if they own their associated memory, and upb_array has a generic pointer for memory management purposes like upb_msg does. | |||
2009-08-07 | Major refactoring of upb_msg. Temporary functionality regression. | Joshua Haberman | |
There is significant refactoring here, as well as some more trivial name changes. upb_msg has become upb_msgdef, to reflect the fact that a upb_msg is not *itself* a message, it describes a message. There are other renamings, such as upb_parse_state -> upb_stream_parser. More significantly, the upb_msg class and parser have been refactored to reflect my recent realization about how memory management should work. upb_msg now has no memory management, and a memory mangement scheme (that works beautifully with multiple language runtimes) will be layered on top of it. This iteration has the new, read-only upb_msg. upb_mm_msg (a memory-managed message class) will come in the next change. | |||
2009-07-22 | Compiler finally works (except string arrays). Untested. Holy crap that ↵ | Joshua Haberman | |
was a lot of work. | |||
2009-07-20 | Move upb_array into its own header, upb_context parses fds instead of fd. | Joshua Haberman | |