Activity for Alexander Vdolainen
-
Alexander Vdolainen committed [e78ada]
snadd() function;
-
minor comments;
-
merge with 1.3.3;
-
Add helper function to parse S-expressions in mem
-
Description for new cstr wrapper is done.
-
stupid error fixed in destroy_cstrwrap();
-
Finally, I need to add doxygen style description and that one will be done. Just a reminder here.
-
Test stage 1
-
a little bit better
-
get_one_sexp() is better now;
-
Functions are done. It's ugly written, however it works. Will try to make it better.
-
Added cstrwrap wrappers functions. it's dirty but quick implementation;
-
Added new API functions prototypes;
-
Removed automatically copied file INSTALL;
-
Well, finally it will be named as sexp_cstrwrap_t. already in the rep.
-
Added a structure for the cstr wrapper;
-
Add helper function to parse S-expressions in mem
-
Finally I'm need it in one my pet project. So, it's going to looks pretty determined. To do so I need to: create a structure, let's say cstrwrap, functions for this are: cstrwrap_init() and cstrwrap_destroy(), and readsexp_cstrwrap() that actually uses it.
-
Use hardware ops for bitwise functions
-
Manual pages for usrtc, list, index allocation
-
Manual pages for usrtc, list, index allocation
-
Changes below:
-
Manual pages for usrtc, list, index allocation
-
Update manual pages/examples/tests for usrtc
-
Update index alloc manual, tests and examples
-
Manual pages for usrtc, list, index allocation
-
Code style compliance
-
Code style compliance;
-
Version number increase;
-
Code style compliance
-
Code style compliance;
-
Update index alloc manual, tests and examples
-
Update index alloc API
-
Update manual pages/examples/tests for usrtc
-
Clean-up and optimization for usrtc API
-
CTries implementation
-
Use hardware ops for bitwise functions
-
Use hardware ops for bitwise functions
-
Provide hw-accel. functions for bitwise ops
-
Test part no. 0
-
BUG: idx allocator doesn't allocate ids in some cases(1/2 full)
-
Few things --- there are:
-
BUG: idx allocator doesn't allocate ids in some cases(1/2 full)
-
Test part no. 0
-
Remove locking from index allocator
-
Remove locking from index allocator
-
Remove locking from index allocator
-
Cleanup unused stuff and update info
-
README updated;
-
I fought my laziness: names are in place;
-
INSTALL is not a part of source tree;
-
Cleanup unused stuff and update info
-
Cleanup autotools stuff
-
Increase version number;
-
Debianization removed, it's not maintained anymore;
-
Removed obsolete comments, contact info updated;
-
Fixed issue with autotools, AC_LANG_...
-
Test part no. 0
-
Cleanup unused stuff and update info
-
Cleanup autotools stuff
-
CTries implementation
-
Examples (part 1)
-
Manual pages for usrtc, list, index allocation
-
Debianization
-
didn't see the reason to do so.
-
Manpages
-
Done: ndbuf_free, ndbuf_free_item, ndbuf_new, ndbuf_new_frombuf, ndbuf_new_palloc, ndbuf_new_wmops
-
Update and fix autotools
-
Minor formatting fixes;
-
Minor updates in misc files, version update;
-
Add helper function to parse S-expressions in mem
-
Update and fix autotools
-
Faststack memory alloc is configure option now;
-
Removed register disable macro (obsolete);
-
Fixes -I in Makefile.am;
-
Fixes for -I in MAkefile.am;
-
Add UDPv6 watchdog socket support
-
Add UNIX socket watchdog support
-
Add TCPv6 support for watchdog
-
Let it go, first alpha commit;
-
Autotools build fix;
-
Autotools update;
-
Added: ndbuf_free_item manpage;
-
Added: new flag NDBUF_MOLS - if applied it will use allocless/memcpyless
-
Added: ndbuf_free_item() function to free in a proper way e.g.
-
ndbuf_free_item implementation
-
Create memcpy less reading
-
ndbuf_free_item implementation
-
NDBUF_MOLS should be used in order to avoid alloc/memcpy for s, p and P types. use it with care
-
Version update: new things are added, time to increase version number;
-
Create memcpy less reading
-
Added: Manpages directory and manpages for:
-
Added: NDBUF_RORB flag is a read-only aware flag. Set this to avoid
-
Manpages
-
it's a time to begin with that. I will add a special manpage for "memory-less" parsing function later - meaning this task is closed after this.
-
Read-only ndbuf
-
More common sense is came: it was done via additional checking and special flag. It's just to avoid stupid errors during the workflow with binary packed buffers.
-
Manpages
-
Add possibility to use user defined memory ops
-
Read-only ndbuf
1 >
