Table Class Testing
DescriptionThe table class is one of the trickier classes because it has quite a few extra functionalities. This task covers 2 things.
1. Check how the original behaves when you try to access (get or set) data with one or more indexes outside of the boundaries (e.g. make a table with dimensions 2, 2, 2 and try to access 3, 2, 2 or something like that). This behavior needs to be implemented if necessary. Currently there are no limitations, no clamping and actually you can access data like this even though it should not be possible.
2. The class needs to be tested. Make a table, run some tests, check if everything behaves normally. Try creating and destroying the table (such as creating within a function and after the end of the function, call GC.start). I suggest that you add zer0::log calls in the creation (rb_new) an destruction routines (gc_free). Remember to temporarily include zer0.h if you call zer0::log.
PriorityHigh.
PrerequisitesNone.
AssignedRyex
Everything elseRefer to
this topic for the first part of the task.
Don't forget to implement x, y, z limitations using hclamp if you find out the real RGSS does not throw errors when the indexes are out of the boundaries.