Coding workflow and reading practices
Hi Johan,
In the thread on GObject instantiation you happened to raise an interesting issue that probably warrants some good discussion.
You had mentioned that adding more to the headers "Saves some time wading through lengthy .cpp files only to find an almost empty function". Do you think you can expand a little on your use case where this type of practice is an issue? That is, can you give a quick description of some of the steps you would be going through when this problem pops up?
I know that different people have different learning and processing styles. (As an extreme example I've even worked with someone whose workflow was impacted by a change in Emacs that limited the number of open windows to only a couple hundred.) It would be good to be sure that we try to get things structured well for easier maintenance, etc.
Thanks.
participants (1)
-
Jon Cruz