|
 |
On 27-4-2018 13:57, Bald Eagle wrote:
> dick balaska <dic### [at] buckosoft com> wrote:
>
>> It's actually a case that happens a lot.
>
> Yeah, I've run into this issue with closing curly braces }
Don't get me started!
>
> That's why I really double-down on structuring my code with noticeable
> indentations, comments on closing braces and #ends, and embedding #debug code
> blocks into the various sections.
>
> Embedding "opening" and "closing" #debug messages for macros and include files,
> writing values of arguments passed to these to the #debug stream, and the
> results of critical intermediate and final calculations can be a huge help in
> tracking down what went wrong, where, and why.
>
> Don't start writing your cvode assuming it's going to work - write it assuming
> it's going to go horribly wrong, and 3 weeks from now when you can't even
> recognize it as your own code or remember what you did or why --- you're going
> to be SO thankful for those comments and helpful debugging features. :)
Oh Boy! Each time I swear to do that and, of course, forget during the
next project. I am a famous re-inventor of wheels if not hopeless
wanderer through a dark code wood. Still, I prevail in the end! ;-)
But, seriously, yes. The best advice to anybody indeed. I am now, when I
revisit an older scene, checking the state of the comments and add them
lavishly when necessary; taking out well-documented code snippets for
later use, etc.
The best checker is yourself.
--
Thomas
Post a reply to this message
|
|
