CodeWeasel's Quick and Dirty Intro to C++

[CodeWeasel]

unfortunately the Beta 2005 didn't have a resource editor, which is what you need to make guis. you said you have 2003? Well, it's easy to MAKE the gui with msvc++ 2003 (just a Project->Add Resource...->Dialog->New away), however implementing it programmatically is more involved. Use the MSDN that was included with 2003, it's VERY helpful in most ways. Do a help search for "Using Dialog Boxes" to get you started.

[scottb]

I am still learning C at the minute but hope to move onto C++ in the next few months!

I am currently using MS Visual C++ 6. Can this be used to create a GUI and would it be worth my while upgarding to the latest version?

Cheers

[CodeWeasel]

Originally Posted by scottb

I am still learning C at the minute but hope to move onto C++ in the next few months!

I am currently using MS Visual C++ 6. Can this be used to create a GUI and would it be worth my while upgarding to the latest version?

Cheers

and upgrade would give you better access to the .net platform and more options for the resource editor, but you don't need that now.

MSVC++ has a resource editor, you should be able to make guis with it, but you also have to learn to program for it. look at the source for my chat program (link in sig) for an example of DIALOG BOX programming, which is different from creating a window. making a window and a dialog box can both be done all in code, but it's easier to make the dialog boxes w/ vc++s editor. if you're just makin a window it's easier to just use code.

[scottb]

I can't find the resource editor in my version of msc++ 6.

Do you know where i can locate it?

[CodeWeasel]

after makin a project you should be able to just do something like: Project->Add Resource...->Dialog->New

You can't use the resource editor unless you have some sort of resource to edit!

[rds0811]

I like Dev C++ for compiling/editing http://www.bloodshed.net/

[CodeWeasel]

yeah, devcpp is VERY nice, it's almost as robust as VC++, I'd recommend it to all the cheapskates out there as it's free

[Shadowmage]

DevC++ is da 1337!

However, REAL cheapskates get better "free" (eh heh heh heh...) software

[CodeWeasel]

Originally Posted by Shadowmage

REAL cheapskates get better "free" (eh heh heh heh...) software

Got that right.

I just got the WHOLE MS Visual Studio .net 2003 free. And it was legal, too. You believe that? No, really, it was! With the kind of money you pay for college, they practically owe it to ya! Virginia Tech has a bunch of stuff for DL by it's students and faculty, including every flavor of Windows (yes, even the latest (Build 4074, I believe) Longhorn beta ), full VS .net 2003 pro AND full VS .net 2005 beta (pro, not express), Norton Anti-Virus, and a hell of a lot more, all full versions.

[jeremy]

i just bought the "C++ for Dummies!"

awesome book..
cool tutorial dude

i havent gotten to the "windows applications chapter" yet, how do i make text display on a Windows app... just normal text.. ya know?

cout << "Moo?";

something like that? like i have DevC++ and it has a template and etc...

[CodeWeasel]

I've finally updated the guide! It now has half of the section on loops, and a link to Dev-C++ near the beginning. Very good IDE, indeed.

Hey jeremy, there are a LOT of ways to output text in a windows application, you need to be more specific with what you intend to do with that text. then I can tell you the best way of going about outputting that text. k? feel free to pm, if you'd like.

[-DeathBlow-]

Jeremy, you have to make sure to type std:: before the cout<<
but, if you dont want to do that type using std::cout;
after your opening bracket ({) in the beginning of the program
example:

 #include <iostream> 
 int main() 
{ 
using std::cout; 
cout<<"Hello\n"; 
return 0; 
}

Codeweasil, im having troubles going about adding the code to dialog boxes like, say i have a simple dialog box, And i want to add the text "Welcome" in msvc++ where would i type cout<<"Welcome\n"; so it would appear on the box?
thanks.

[CodeWeasel]

Originally Posted by -DeathBlow-

Jeremy, you have to make sure to type std:: before the cout<<
but, if you dont want to do that type using std::cout;
after your opening bracket ({) in the beginning of the program
example:

 #include <iostream> 
 int main() 
{ 
using std::cout; 
cout<<"Hello\n"; 
return 0; 
}

Codeweasil, im having troubles going about adding the code to dialog boxes like, say i have a simple dialog box, And i want to add the text "Welcome" in msvc++ where would i type cout<<"Welcome\n"; so it would appear on the box?
thanks.

you don't use cout at all in a purely windows application, so you didn't help jeremy at all, i'm sorry to say.

if you have a dialog box and you want STATIC text all you have to do is make a static text control and type what you want displayed in the properties area. i've attached some screenies of what i did for the weaselchat version number and all that in the bottom left of 1.2

it's funny, I could really help you guys out but typing everything and makin screenshots is a pain in the *** i wish there was some way to show you in person...

[CodeWeasel]

Just updated the guide to address For loops in the loop section. Next will probably be a section on strings and arrays. Then perhaps info on declaring classes and structs... then maybe data structures... man, so many things to talk about

[JoeV2-MCM]

Pretty good "quick 'n dirty" intro to C++, CW.

Some suggestions you might consider incorporating...

1) Rather than explaining to the reader why they might have to change your first example from "void main() { ... }" to "int main() { ... return 0; }" for certain compiler implementations (specifically those that are strictly ANSI compliant by default), which may lead to confusion for some, how about you simply consider changing the initial example to "int main() { ... return 0; }". Then you can simply leave out the explanation altogether. After all, this is how the ANSI C++ Standard specifies main is to be declared regardless of its build / runtime environment.

2) This is very important. The "double" data type does NOT truncate any value in the variable to two decimal places. I'm sorry but I got a very big smile on my face when I read this sentence. For a 32-bit compiler, the biggest difference between a float and a double is the amount of memory space each type occupies. Specifically, a float is 4 bytes wide and a double is 8 bytes wide. A quick 'net search can find the range of values associated with each data type but you can imagine a double has a greater range than a float.

3) "if(iTotal > 7 || iTotal < 7)" is basically the same as "if(iTotal != 7)", right? I realize you were just trying to provide another example but I wanted to make a point (i.e. always tries to write clear, self-documenting code).

4) Also, parentheses are your friend. I would prefer to see someone write this line as follows: "if((iTotal > 7) || (iTotal < 7))". Heck, I would've written it this way. Why? Well, there are several reasons but the main one is probably the notion of operator precedence. I realize the topic of operator precedence is too "complex" to bring up at this point in your document but since your laying the groundwork I felt the use of too many parentheses is this particular statement might be better, IMHO.

Just my two cents. Hope you find it useful. Joe

[CodeWeasel]

Thanks for the input!

Originally Posted by JoeV2-MCM

Pretty good "quick 'n dirty" intro to C++, CW.

Some suggestions you might consider incorporating...

1) Rather than explaining to the reader why they might have to change your first example from "void main() { ... }" to "int main() { ... return 0; }" for certain compiler implementations (specifically those that are strictly ANSI compliant by default), which may lead to confusion for some, how about you simply consider changing the initial example to "int main() { ... return 0; }". Then you can simply leave out the explanation altogether. After all, this is how the ANSI C++ Standard specifies main is to be declared regardless of its build / runtime environment.

Yeah, I've been playing with this change for awhile now. I suppose I should just save confusion and make the fix.

2) This is very important. The "double" data type does NOT truncate any value in the variable to two decimal places. I'm sorry but I got a very big smile on my face when I read this sentence. For a 32-bit compiler, the biggest difference between a float and a double is the amount of memory space each type occupies. Specifically, a float is 4 bytes wide and a double is 8 bytes wide. A quick 'net search can find the range of values associated with each data type but you can imagine a double has a greater range than a float.

Bah! My mistake...Maybe I was too tired? Wonder what I was thinking...prolly some confusion between C++ and TI-89 Calc crap. Yeah, here's the official definitions of Float, Double, and Long Double (which I will edit into the guide):
Float - 4 Bytes - 3.4e + / - 38 (7 digits)
Double - 8 Bytes - 1.7e + / - 308 (15 digits)
Long Double - 10 Bytes - 1.2e + / - 4932 (19 digits)

3) "if(iTotal > 7 || iTotal < 7)" is basically the same as "if(iTotal != 7)", right? I realize you were just trying to provide another example but I wanted to make a point (i.e. always tries to write clear, self-documenting code).

Yeah, it was for example purposes, I usually use != unless there's some weird requirement, or in this guide

4) Also, parentheses are your friend. I would prefer to see someone write this line as follows: "if((iTotal > 7) || (iTotal < 7))". Heck, I would've written it this way. Why? Well, there are several reasons but the main one is probably the notion of operator precedence. I realize the topic of operator precedence is too "complex" to bring up at this point in your document but since your laying the groundwork I felt the use of too many parentheses is this particular statement might be better, IMHO.

Good point. Should basically tell 'em to write like they would on a graphing calc, eh? Maybe it's because I've just been using switch statements a lot lately...

Just my two cents. Hope you find it useful. Joe

Very useful, thanks Joe!

[CodeWeasel]

Ok I have made the changes mentioned in the above post, look good now, Joe?
I'm also trying to put together a good section on arrays/strings, so look for that in the future. Maybe a little farther into the future, cause I'm movin' out to college tommorrow! Here comes Heaven AND Hell, all rolled into one...

[runlinux]

hey, when are we gunna get into structs, classes, inheritence and possibly the coolest things ever : POINTERS!!!! ?

[CodeWeasel]

I've been pretty busy as of late with college and all, believe me, I'll update when I get a few hours free.

[CodeWeasel]

Mkay! Finally updated with info on strings and arrays. Next will be structs...