Sorting and Detection for whether Sorting elements needs to be done isn't accurate


It performs correctly on the test project but not on others.

After figuring out where test case has a gap, add a file that covers that test case.


mcaden wrote Jun 24, 2011 at 7:10 PM

It appears as if visual studios access enum isn't in order like I expected it to be. I'll have to map it out. Additionally it looks like in detection everything is being compared to the first item rather than the item previous to it. it looks like something isn't being set right.

mcaden wrote Jun 24, 2011 at 7:12 PM

I've remapped the access levels to be in the appropriate order, double checked the comparison in actually sorting the values, and removed the setting of the previous value from an else to put it so that it always sets the previous item.

I've added 3 more test cases:
  1. No sort needed
  2. Sort needed, all are wrong
  3. Sort needed, first item is a private field
All currently pass.

mcaden wrote Jun 24, 2011 at 7:34 PM