Google Code-in

Even if you don't know C, check this code snippet:

typedef struct _avistdindex_chunk { char fcc[4]; // ix## u32 dwSize; // size of this chunk u16 wLongsPerEntry; // must be sizeof(aIndex[0])/sizeof(DWORD) u8 bIndexSubType; // must be 0 u8 bIndexType; // must be AVI_INDEX_OF_CHUNKS u32 nEntriesInUse; // char dwChunkId[4]; // '##dc' or '##db' or '##wb' etc.. u64 qwBaseOffset; // all dwOffsets in aIndex array are relative to this u32 dwReserved3; // must be 0 avistdindex_entry *aIndex; } avistdindex_chunk;

You can see that the code is hard to read because the // (what follows are comments) are not aligned. The job is to go through the code and make it more readable and pleasant to the eye without changing what it does.

You can do it manually or you can find a tool that does it for you. No shame in figuring out a way to do less manual work as long as the results are good.

Once you have done this, send a pull request (in GitHub) with the changes.

By doing this you will be practicing a few things: Using GitHub, pull requests, getting used to editing code and looking for tools.

The repository is here: https://github.com/CCExtractor/ccextractor

Please start by working on the .h files inside the directory src/lib_ccx