Products > Programming

Question about DEV-C++

(1/2) > >>

Greetings from a code newbie. I downloaded the 48MB DEV-C++ and have set it up and really like it. I noticed during the unpacking phase that there were hundreds of files ending in .py which to me indicates a Python script. Is that correct? As such does that mean there may still be some sort of Python engine remaining on my computer that would allow me to run Python .py files? I am using the SAMS Teach yourself C++ in 21 Days book and I noticed I don't have to include the '.h' for instance <iostream> works but <iostream.h> as called out in the book results in an error. I looked in the directory containing the '.h' files and there are only maybe 20 files in that directory, however the directory where 'iostream' with no apparent suffix is located has hundreds of files. I am a circuit designer having worked for several major companies and the CPLD and FPGA work I did was mostly routing logic and I used 'Schematic Capture' laying out the building blocks I was familiar with. I spent many long years writing 8080/8085A Assembly Language and progressed to Visual Basic for some user interface on-screen radio buttons to perform dedicated switching tasks. Thanks for your inputs to my questions!! I would like to understand more about what my code writers are doing with the boards I designed to meet their hardware specifications.

The files likely come with gdb. Gdb can use Python as its scripting language and the release in Dev-C++ seems to come with both Python interpreter library and a rich collection of scripts. Note however that there is no Python executable present. So you can’t run a Python script as-is with that; the library is meant to be used from other programs (in this case: gdb).

If a book (or any other source) even mentions things like “iostream.h”, use it as a paper weight or a support for the monitor. Or put it on your curiosity shelf, beside an 8" floppy. :D Saying it’s outdated would be a grave understatement. It describes an early version of C++ from Stroustrup, basically a prototype, which has little to do with any C++ version used in practice.

And no, it’s not only a matter of different file names. The contents of these files, the general architecture, the concepts behind it, even the language itself: all this is different.

Unfortunately I can’t help with choosing the right book anymore. But even when I could — over 8 years ago — the above warning was already accurate.

Obligatory comic from Abstruse Goose regarding learning C++ in 21 days. ;)

Oh the good old DEV-C++. This was all the rage when I was in university. I completely forgot about it.

DEV-C++ wasn't my first choice however, my 'knock about' laptop is an old Gateway ROG-450 32 bit machine. I dearly hang on to it as it has VGA and composite video outputs as well as a real 9 pin serial port and 25 pin parallel port, 2 USB ports and a good quality sound card with mic + Line in + headphone / audio out and good built in speakers. I also have the DVD reader / CD-CDR reader/burner and a plugin floppy drive! It has many scientific programs like MatLab and all of my older Xilinx ISE and so forth. I have a ton of ham radio programs for SSTV-CW-WEFAX and I can even plug it into the video projector at the Masonic Lodge and play video or step through .jpg images during ritual practice. It is stuck at XP-SP2, nothing newer and it never goes online but I can tell you it is the hardest working horse in my stable!! Cheers mates!!

In 2005 in my college Dev-C++ was used as the default IDE for C++. I don’t recall any serious problems with it. I don’t think there were any drastic changes since then, so it should still be fine.

While personally I developed dislike for IDEs, a lightweight program in Dev-C++ style seems well suited for learning. Not overloaded with features, allows for quick write-test cycle, hides parts not important to the newcomer.


[0] Message Index

[#] Next page

There was an error while thanking
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod