Skip to content

API extension and portability #7

Closed
wants to merge 1 commit into from

2 participants

@rockwarrior
  • added user callback to API so that the application does not need to buffer large arrays of offsets and lengths
  • written in ANSI c for portability on non-gcc compilers
  • reduced footprint size by 50% by using switch statement instead of tables
  • does not allocate any memory at all, except return code
  • added c++ support
Max Shaffer * written in ANSI c for portability on non-gcc compilers
* reduced footprint size by 50% by using switch statement instead of tables
* does not allocate any memory at all, except return code
* added user callback to API so that the application does not need to buffer large arrays of offsets and lengths
* added c++ support
4f0586b
@quartzjer
Owner

I was tempted to go this direction with v2 and move away from the tables, but instead streamlined the api to match how it's been most commonly used (just to retrieve the offset for a particular key w/o using memory).

I may end up coming back to this style for a future version, but is it ok if I close this pull req for now?

@ghost
ghost commented Oct 16, 2014

Sure, no problem.

@quartzjer
Owner

Cool, thanks! Also, since you're obviously good at C, and might be interested in such things, would love any feedback on my telehash-c v3 branch (it's a work-in-progress).

@quartzjer quartzjer closed this Oct 16, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.