Is C++ free language or U have to buy it

[‚΂©‚Ì2000]

Hi everyone I'm trying to learn C++. I've started learning Java but now i wanted to learn C++ at the same time.

This way I think it going to be faster in learning both language cos they are close to the same language. well that what i heard.


I don't know anything about C++ and I don't if it free or not.
I wanted to know the price, the newest version (Not Visual C++) Plz

Thanks you

[parksie]

C++ is free, totally and unequivocally It's just compilers you pay for if you really want to, but you don't need to. See the FAQ for some links, but there's DJGPP, Borland C++ 5.5, Cygwin, and some others. (PS: lots of things use the GNU C++ Compiler although they have different names)

[Vlatko]

If you are looking for i free C++ compiler i would recommend Turbo C++ 3.0, it is great. Otherwise if you have money or you live in some third world country get MS Visual C++ (absolutely the best).

[parksie]

Isn't TC++3 16-bit? I don't think we want to scare new learners away with near/far pointers...

[Vlatko]

Yeah, parksie you're right. I use it a lot in the past few months (need to make DOS apps), so i forgot about 32-bit programming.

[parksie]

Can't you use DJGPP to make DOS apps or do they actually have to be 16-bit ones?

[denniswrenn]

Ummm, DJGPP compiles console apps...

[parksie]

Nope, it makes protected-mode DOS programs

[denniswrenn]

Then why are they so big? I thought only console programs were >150kb (The program I made in DJGPP was a "hello world" program, and it was like 175kb)...

[parksie]

Did you remember to use the -s command line option?

[denniswrenn]

I was using RHIDE(the IDE) so I didn't really have a choice of any switches.... what does -s do?

[parksie]

It strips all the debugging symbols out which GPP uses by default. Also, the C++ RTL is a lot larger than the C one - try a "Hello World" in C and it's about 50K as opposed to about 150K in C++ (just tested now, using the -s option both times).

[Emo]

Originally posted by parksie
near/far pointers...

I did a tutorial a while ago and it introduced me to the basics of Pointers and how to use them, but it didn't mention this... what does it do and what's if for?

Thanks!
-Emo

[Bjwbell]

I don't know anything about them; except i've heard they're quit nasty. i believe they had something too do with segments?
As far as i know you don't have too worry about them with win98.

[parksie]

Yep. A near pointer is to memory within the current segment, but a far pointer is a combination of segmentffset One of the nastiest things Intel ever did, but they seem to have got over it

They're unnecessary in 32-bit programming of any kind.

[The Hobo]

Are there any programs that aid in writing C++ files before compling?

[parksie]

Notepad

Most compilers come with an IDE now, although the Borland free one doesn't. Denniswrenn made an IDE, you'd have to see him about it.

[denniswrenn]

http://www.planetsourcecode.com/xq/A...s/ShowCode.htm


Note: It does not compile the program in the large edit box, you have to type the path in the Open/Save box....

[wossname]

Dennis, in RHIDE, go to Options...Compiler Options and put -s in there. I did that and now my hello world program is 137kb in size (down by half!). Why the hell is it still so big though?

[The Hobo]

How do I get Borland Compiler to work?

[parksie]

Originally posted by wossname
Dennis, in RHIDE, go to Options...Compiler Options and put -s in there. I did that and now my hello world program is 137kb in size (down by half!). Why the hell is it still so big though?

I think it's because it also includes a DPMI server to enable your program to run 32-bit under DOS. Windows includes a DPMI, so native Windows programs are much smaller. Plus, it includes all the runtime library information it needs - it's larger, but totally independent.

[Zaei]

Dont bother trying to look for TC++ 3. It took me a few hours to find it, and the newer 32 bit compilers will work better for most people. Although i really like "graphics.h"... How odd does "256 colors on a monochrome screen" sound?

From what i can tell, i think they had to separate pointers into near and far because they could only transfer 16 bits per memory access (an int), so it would take 2 memory accesses to get an entire 32 bit address. Nowadays, we grab 32 bits per memory access (a DWORD). Sorta like the reason BOOLs are really one byte long, instead of a bit, because you cant access one bit at a time.

Z.

[parksie]

Although on an Intel architecture I believe that although they're a byte, they effectively take 4 bytes because all variables have to lie on a 4-byte boundary or something like that.