Comments in the code? about devilution HOT 6 CLOSED

Absolutely.

from devilution.

Eventually, but not a priority. I've tried to only add comments where there are decompiler errors, to help make them easier to spot. I'd prefer to keep it this way for awhile so self-explanatory functions don't get clogged. E.g.

if( leveltype == LT_CAVES ) // if the level type is in the caves
{
    if( player == myplr ) // if the current player is my player
    {
        CastSpell(SPELL_TOWNPORTAL); // cast town portal
        PlaySFX(SOUND_PORTAL); // play town portal sound

from devilution.

As this is C++ and not C# I would still stick to Dennis Doomens Guidlines for commenting code AV2310 & AV2316

https://csharpcodingguidelines.com/documentation-guidelines/

from devilution.

I would like to see comments on address spaces in the original exe . this will make it easier for me when I say need to look at the original function in asm.

from devilution.

I would like to see comments on address spaces in the original exe . this will make it easier for me when I say need to look at the original function in asm.

This was part of the original source (as taken from the decompiler), but was removed in rev 49a6f4f and superseded by Support/surgery.xls.

I wouldn't mind if these addresses were added again to the source code to facilitate reversing. Later when we hit 1.0 they can be removed. What do you think @galaxyhaxz?

from devilution.

Yeah it might be a good idea to add those back at least to the .h files. We'll add comments later on as everything is gradually cleaned up.

from devilution.