Today was the beginning of what would be my dual pronged effort during winter break; to manage EEG reading applications on Unity and study more effective C++.
For the EEG readings, I mainly familiarized myself with the information. Unfortunately, the readings seem to be in large blocks of text instead of anything specifically corresponding to positive/negative readings, and the reward system seems not to be reading either. I've gotten the procedural skybox to change color on command, so the visuals seem to be all set for the upcoming data.
As for Effective c++ learning, I've learned to store resource allocation in standalone statements (since we can't trust the order that compilers will work them out) and went through some vague atrocity regarding interface design. Passing by constant reference instead of value definitely helps, especially with the hidden overhead involving copying data. However, especially with the tricky nature of deleting local objects, it was best to return a value. I also thought through the section on the importance of private members, and have always felt off regarding encapsulation only as a means to hide data. (So many times when I wish I would access data but can't) Instead, encapsulation involves the ability to update an implementation (a function) across an entire project, and can put more in a get/set than just getting and setting.
Privatizing data is OK (and actually fairly annoying from a client standpoint), but I can see where encapsulation is a lot more than privatizing data.
No comments:
Post a Comment