Beginning Visual C++ 6.0 by: bs0d

Page: 1 of 10 (View All)

Introduction

This tutorial is going to cover the basics of Visual C++. I will be covering alot of the basics, so this should be a good start to anyone wanting to learn C. I could go into more details on all the functions, classes, objects ect. but that is another article for another time.

How it works...

Visual C++ 6.0 is designed to help you build your C++ programs and has a debugger and compiler and everthing all in one, so you dont have to bother with any of that. The source code you write will be saved in a file with a .cpp extension (the cpp stands for C plus plus). The compiler will translate the higher-level instructions you wrote into machine language ( 1's and 0's). This is what the computer doesunderstand. So when you compile the program, the compiler will aso create a file with a .obj extension (obj for object). And finally, once the compiler creates the object file, the linker is then executed. The linker will take the object file and combine additional machine code nessary for it to run correctly, and an executable file is then created, which has an extension of .exe (exe for executable). If all is well, you can run the .exe file over and over without need of anymore translating and such. This is your final product.

Algorithms, Flowcharts and IPO Charts

I have worked with numerous programming languages. Each time you're learning the code; programs, flowcharts, or algorithms will be mentioned to help you in the design process. Generally, I would ignore these because it was easier for me to write the program, and if it was required, I would go back and whip up a flowchart or algorithm. However, when I began learning Visual C++, It does help if you're at a beginning level to use these to your advantage.

Flowcharts and algorithms are not the only way to plan out your program. Programmers also use what are called IPO charts to organize and summarize the results of their problem analysis. IPO is for Input, Process and Output. This is a simple table that has 3 columns. The first column is Input. In this column, place what you will need as input for the program. What data will be required as user input, like hours worked, or rate of pay. Then, the second column is Processing and processing items. This is where you will make up an algorithm for how your program will work. The processing items will be like counters, ect. Finally, the third column is for Output. What will your results be? What do you need to show to the user. This data will be here.

This is all to help you out, and as you begin to disect various programming problems you will get better each time and eventually, you may begin to shy away from IPO charts, and that of the like. But even further on, you may find them quite useful to break down really large programs that you need to work on.