anubhavashok / allocator Goto Github PK

The GitHub repository comes with an issue tracker.
Create an issue for each of the requirements in this table. Create an issue for each bug or feature, both open and closed. Describe and label each issue adequately. Create at least 10 more issues in addition to the requirements in this table.

in:

1. valid

1. find free space
2. change sentinels
3. change free space sentinels

Write unit tests before you write the code. When you encounter a bug, write a unit test that fails, fix the bug, and confirm that the unit test passes. Write at least an average of 3 unit tests for each function. Tests corner cases and failure cases. Name tests logically. You must use Valgrind.

change cast types to reinterpret cast, reduce casting

1. get size
2. set up start sentinel
3. set up end sentinel

1. check sentinel
2. jump to end
3. make sure start sentinel == end sentinel
4. repeat till end of array

function which takes in left and right pointer
joins both blocks

Use Doxygen to document the interfaces.
The above documentation only needs to be generated for Allocator.h. Comment each function meaningfully. Use comments only if you need to explain the why of a particular implementation. Choose a coding convention and be consistent. Use good variable names. Write readable code with good indentation, blank lines, and blank spaces.

Set up a private Git repository at GitHub, named cs371p-allocator.
Invite the grader to your repository. Commit at least 5 times. Commit once for each bug or feature. If you cannot describe your changes in a sentence, you are not committing often enough. Write meaningful commit messages and identify the corresponding issue in the issue tracker (below). Create a tag for important milestones (e.g. without a cache, with a lazy cache, etc.). Create a log of the commits. Push frequently. It is your responsibility to protect your code from the rest of the students in the class. If your code gets out, you are as guilty as the recipient of academic dishonesty.

Rename "makefile.c++" to "makefile".
Fill out the Google Form and submit the ZIP file to Turnin.

recheck all types and the arithmetic

Check edges in coalesce to prevent taking left or right pointer OOB.

1. change signs of sentinels
2. coalesce

Change all pointers to char?
Make it more readable

Use assert to check pre-conditions, post-conditions, argument validity, return-value validity, and invariants. Worry about this last, but your program should run as fast as possible and use as little memory as possible.

If a block has free space but not enough for a new block, allocate the whole thing