Author: Unknown
Subject: DestroyD
Date: Tuesday, 31 Mar 2020, 11:49:04

Based on your last response, if we don't free(line) where line is the char * being inputted into remD (inside of our destroyD function), won't there be valgrind errors due to unfreeze memory once we destroy the deque? The way I have it now overrides the same char * each time I call remD from destroyD.