cthulhu-bot/Dunwich — Issue #1: RFile access
Author: cthulhu-bot
Created: 2012-03-09 08:57:34+00:00
State: open

Obviously we want to restrict file writing access unless absolutely necessary. Current issue revolves around wanting to hide RFile initialization. This presents problems because then only 1 class may instantiate the RFile accessor class if the physical files get initialized in the constructor. Any other initialization will wipe what's already been written. This means if RFuncs is defined as the "accessor" class then every object must have a cooresponding "WriteObjectXToFile" method in RFuncs built solely to write that specific class of objects to file. Seems kinda stupid but the more I think about it it kinda makes sense. For RVector adds we could have a WriteVectorAdd and could pass the internal RVector list and add objects as needed.