Code center > Darwinbots Program Source Code

Overflow etc.

<< < (2/2)

Ulciscor:
I really wouldn't trust myself to code anything really serious.

PurpleYouko:
Believe me, the "stupid" Italian bits don't really make much difference to a general understanding of the code.
Num and I have probably spent well in excess of your 200 hours getting a real grip on this program. Once you get to that point though, the Italian text just kind of fades from view like it was never there. The code is self explanitory without the comments.

The most tricky thing is usually tracing a procedure call back to its ultimate origin and then figuring out where a particualr variable class was defined and in which module.

Just try tracing the defining point of "mutarray" to change the number of elements that it contains and then add a new one and go through every instance of it in the entire program to modify the calls.

I have had to do this 3 times now and my brain hurts just thinking about it.  :wacko:

Ulciscor:
My main fear would be that adding one tiny procedure would mess up something somewhere else in the program.

Numsgil:
You never know until you try.  As long as you approach the code as an incomprehensible whole with lots of little, easilyunderstood pieces you can usually start changing things.

Anyway, PY or I can check over any new code someone else's done to see if it screws up something else.  It's not terribly difficult.

Check out the Awaiting Programming subsection is suggestions for ideas I've gathered that aren't terribly difficult to achieve first time programming.  Like Setting body points at sim start.

PurpleYouko:

--- Quote ---My main fear would be that adding one tiny procedure would mess up something somewhere else in the program.
--- End quote ---
Happens all the time.
Why do you think we still have bugs to fix?
You makes yer mistakes then you fix 'em. Only way to learn.

Navigation

[0] Message Index

[*] Previous page