Member No.: 1938
Joined: 12-January 06
Sometimes a visual is the best way to truly understand a concept ----
I have been treating each routine as an individual program. Tack on a test to the beginning and make sure it works. Routines that used other routines would still have the setup and test in the most recent routine. ml file file file ... link file file file ... edit, rinse and repeat. I brought my command prompt mind set to the IDE.
Well, because of this little quirk I moved the setup, test and exit instructions to its own file and called it my main program with the same project name as the file. I just considered this the best and most correct work-around for what was ailing me. Now in program properties just Assemble file file file .... and Link file file file ... and 'Make -> Go All' works great and I am a happy camper.
Then I noticed the link 'Module' in a context menu. Hmm, I wonder ... Whoa. This is a beautiful thing. No more file file file anywhere. No more command prompt. just write the routine, setup the Main/Test program and click 'Go All'. While I was basking in my euphoria a light clicked on and I suddenly 'truly' understood something I just thought I understood before....
From now on I will be known as Modular Man
I know enough about programming to be really dangerous and when it comes to machine language I can generate self-eating code with my eyes closed.
I knew I needed an IDE environment to be able to help me learn more and WinAsm has to be the greatest find on the internet of any catagory. Since starting to use it there hasn't been a moment go by that I haven't learned something. Thank you for such an excellent product and a great environment here in which I can learn from everyone.
Ahhh, the beauty of modular design... Now if I could only get this structured programming thing out of the way - sigh