ak149 no IO code MALLOC: simple and good best-fit ; good tester :-) az17 nothing submitted bmc16 MALLOC: your tester sometimes requests blocksizes larger than the max ; may make to many requests ; could simplify iteration to: for (Map.Entry pair: size.entrySet()) total += pair.getValue(); bws5 no IO code MALLOC: interesting allocation strategy ; tester ignores numberOfRequests, cph4 IO: hard-coded file name, MALLOC: your tester may exceed maxNumberOfLiveWords dmt17 no IO code MALLOC: you must have mis-understood the specs ; your tester may exceed maxNumberOfLiveWords dsh8 MALLOC: you can use Arrays.fill( memory, false) instead of an explicit loop; your alloc can corrupt allocations; test logic for free is flawed ejd9 IO: result table is missing, MALLOC: efficient best-fit implementation! hjg10 IO: well-structered IO code, MALLOC: good allocator; but your tester is too simple jdb29 IO: no result table, buggy code, MALLOC: you must have mis-understood the specs ; your tester may loose failures jlm47 IO: hard-coded file name , MALLOC: good allocation code ; tester may not make numRequests jps22 well done! jr94 no IO code MALLOC: simple first-fit ; but fails some of my tests kgas1 MALLOC: your alloc seems buggy; tester insufficient: e.g. why only free(0)? kjjg1 MALLOC: solid first-fit; but tester may exceed maxNumberOfLiveWords lb65 IO: not outputting command list, MALLOC: best-fit ; but quite inefficient mdb29 MALLOC: your alloc can corrupt memory mfb3 MALLOC: probably the most complex code for this assignment mfma2 MALLOC: simple allocator is ok ; but tester is buggy; e.g. can increment failcount without calling alloc??? mjh77 MALLOC: in a long-lived server your alloc might go astray when wordName wraps around; using a long would reduce the probability of that happening mm236 IO: not outputting command list, MALLOC: your interpretation of maximumNumberOfLiveWords is rather "liberal" mrl13 MALLOC: your alloc can corrupt memory mrr21 no IO code, MALLOC: fails my test msb26 MALLOC: allocator ok; but your tester is too simple njh34 IO: no result table, buggy code, MALLOC: fails my test no15 IO: not much running IO code, MALLOC: your code misses exact fit blocks; your tester "frees" too often ns127 MALLOC: no AllocTest code rdc12 IO: not outputting command list MALLOC: fails my test rgf5 MALLOC: your alloc can corrupt memory ; tester is too simple rgs10 MALLOC: free does not check for correctness; but also does *not* corrupt in these cases; good tester rlb22 well done rsb16 MALLOC: simple allocator; but extensive tester sb144 IO code is buggy: cannot erase more stars than there are; MALLOC: your alloc can corrupt memory ; tester counts illegal allocs as failed sdw14 well done sjv14 IO: not outputting command list, MALLOC: tester counts illegal allocs as failed sk218 MALLOC: tester makes potentially illegal allocs as requestCount can be larger than maximumNumberOfLiveWords src17 MALLOC: tester makes potentially illegal allocs swp4 MALLOC: times out tc99 IO: slight bug: the for loop for i should be 1 to 8, not 0 to 8, MALLOC: simple,but solid tcg4 MALLOC: times out sh212 nothing submitted jag39 nothing submitted