Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Issue 1199: Remove the vestigal traces of custom memory allocators, part 1, updated #11

Closed
wants to merge 1 commit into from
Closed

Issue 1199: Remove the vestigal traces of custom memory allocators, part 1, updated #11

wants to merge 1 commit into from

Commits on May 13, 2015

  1. Issue 1199: Remove the vestigal traces of custom memory allocators 

    1. memry removal.

This should be no-brainer. These functions never seemed to do anything useful. The only oddity was with alloc_string which rounded the allocation upwards to nearest multiple of 4. Based on my review of code, I could not identify any value in this feature, so even alloc_string was simply transformed to malloc.

memry.* are removed. All code is adjusted to simply call malloc and free instead.

listio.* are removed. The list reading function in these files appears to have been unused, and contained the only invocation of strsave define, which was one of the alloc_string users, so I removed both of them.

https://code.google.com/p/tesseract-ocr/issues/detail?id=1199
    @alankila @jimregan
    alankila authored and jimregan committed May 13, 2015
    Configuration menu
    Copy the full SHA
    d0cb4bd View commit details
    Browse the repository at this point in the history