Archived

This topic is now archived and is closed to further replies.

Studying Source Code

This topic is 5515 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi! I''m always reading where people are recommending studying source code when learning to program. I think I know what they mean by this (read it, reproduce it, find out why it ticks) but is there a "method" or procedure for doing this? I want to know how to best benefit from this. Thanks!

Share this post


Link to post
Share on other sites
I found it a great help when i was learning programming. Back in the days when you still started with lowlevel languages and worked your way up. Rather than walking the way down, as most people do now.

I remember having tons of assembler code on disks, printed on miles of tractor paper. Anyhoo, I always took a piece of code that was somehow a bit comprehensive and compiled it. Changed an value here and there and watched what happened. Then i decided that if they could make a square bounce around, I want to make two. So i modified the code until I got what I wanted.

I think the most important thing is to know what you want as a result before you start changing stuff. Nowdays there is internet and you can get whole game sourcecodes etc. But fool around with small snippets and try to modify, merge them. There is no way a beginner will be able to download the whole quake 2 engine and fool around with it. Its way too big, and takes way too much work to do stuff. Keep small goals on your way to the big one.

Also when you study code, do not try to understand the coolest effects etc. Understand whats behind it. Effects are usually small algorithms and stuff youll understand eventually. At the start, study the windows code, how they build arrays, how they set up palettes etc.

- Zorak - Neat Fella.

Share this post


Link to post
Share on other sites