05.01.2021»»вторник

Sample C Program In Dev C++

05.01.2021
-->

Home » C programming language. C programming solved programs/examples. This section contains solved program on various popular topics of C Programming Language.As we know that C is the superset of C language, hence most of the programs already written in C programs section. Dev c example free download. Qmmp This program is an audio-player, written with the help of the Qt library. The user interface is simi.

Visual C++ includes a C compiler that you can use to create everything from basic console programs to full Windows Desktop applications, mobile apps, and more.

This walkthrough shows how to create a basic, 'Hello, World'-style C program by using a text editor, and then compile it on the command line. If you'd rather work in C++ on the command line, see Walkthrough: Compiling a Native C++ Program on the Command Line. If you'd like to try the Visual Studio IDE instead of using the command line, see Walkthrough: Working with Projects and Solutions (C++) or Using the Visual Studio IDE for C++ Desktop Development.

Prerequisites

To complete this walkthrough, you must have installed either Visual Studio and the optional Visual C++ components, or the Build Tools for Visual Studio.

Visual Studio is a powerful integrated development environment that supports a full-featured editor, resource managers, debuggers, and compilers for many languages and platforms. For information on these features and how to download and install Visual Studio, including the free Visual Studio Community edition, see Install Visual Studio.

The Build Tools for Visual Studio version of Visual Studio installs only the command-line toolset, the compilers, tools, and libraries you need to build C and C++ programs. It's perfect for build labs or classroom exercises and installs relatively quickly. To install only the command-line toolset, download Build Tools for Visual Studio from the Visual Studio downloads page and run the installer. In the Visual Studio installer, select the C++ build tools workload, and choose Install.

Before you can build a C or C++ program on the command line, you must verify that the tools are installed, and that you can access them from the command line. Visual C++ has complex requirements for the command-line environment to find the tools, headers, and libraries it uses. You can't use Visual C++ in a plain command prompt window without some preparation. You need a developer command prompt window, which is a regular command prompt window that has all the required environment variables set. Fortunately, Visual C++ installs shortcuts for you to launch developer command prompts that have the environment set up for command line builds. Unfortunately, the names of the developer command prompt shortcuts and where they're located are different in almost every version of Visual C++ and on different versions of Windows. Your first walkthrough task is to find the right shortcut to use.

Note

A developer command prompt shortcut automatically sets the correct paths for the compiler and tools, and for any required headers and libraries. Some of these values are different for each build configuration. You must set these environment values yourself if you don't use one of the shortcuts. For more information, see Set the Path and Environment Variables for Command-Line Builds. Because the build environment is complex, we strongly recommend you use a developer command prompt shortcut instead of building your own.

These instructions vary depending on which version of Visual Studio you are using. To see the documentation for your preferred version of Visual Studio, use the Version selector control. It's found at the top of the table of contents on this page.

Open a developer command prompt in Visual Studio 2019

If you have installed Visual Studio 2019 on Windows 10, open the Start menu, and then scroll down and open the Visual Studio 2019 folder (not the Visual Studio 2019 app). Choose Developer Command Prompt for VS 2019 to open the command prompt window.

If you're using a different version of Windows, look in your Start menu or Start page for a Visual Studio tools folder that contains a developer command prompt shortcut. You can also use the Windows search function to search for 'developer command prompt' and choose one that matches your installed version of Visual Studio. Use the shortcut to open the command prompt window.

Open a developer command prompt in Visual Studio 2017

If you have installed Visual Studio 2017 on Windows 10, open the Start menu, and then scroll down and open the Visual Studio 2017 folder (not the Visual Studio 2017 app). Choose Developer Command Prompt for VS 2017 to open the command prompt window.

Sample

If you're running a different version of Windows, look in your Start menu or Start page for a Visual Studio tools folder that contains a developer command prompt shortcut. You can also use the Windows search function to search for 'developer command prompt' and choose one that matches your installed version of Visual Studio. Use the shortcut to open the command prompt window.

Open a developer command prompt in Visual Studio 2015

C Program In Dev C++

If you have installed Microsoft Visual C++ Build Tools 2015 on Windows 10, open the Start menu, and then scroll down and open the Visual C++ Build Tools folder. Choose Visual C++ 2015 x86 Native Tools Command Prompt to open the command prompt window.

If you're running a different version of Windows, look in your Start menu or Start page for a Visual Studio tools folder that contains a developer command prompt shortcut. You can also use the Windows search function to search for 'developer command prompt' and choose one that matches your installed version of Visual Studio. Use the shortcut to open the command prompt window.

Next, verify that the Visual C++ developer command prompt is set up correctly. In the command prompt window, enter cl and verify that the output looks something like this:

There may be differences in the current directory or version numbers, depending on the version of Visual C++ and any updates installed. If the above output is similar to what you see, then you're ready to build C or C++ programs at the command line.

Note

If you get an error such as 'cl' is not recognized as an internal or external command, operable program or batch file,' error C1034, or error LNK1104 when you run the cl command, then either you are not using a developer command prompt, or something is wrong with your installation of Visual C++. You must fix this issue before you can continue.

If you can't find the developer command prompt shortcut, or if you get an error message when you enter cl, then your Visual C++ installation may have a problem. If you're using Visual Studio 2017 or later, try reinstalling the Desktop development with C++ workload in the Visual Studio installer. For details, see Install C++ support in Visual Studio. Or, reinstall the Build Tools from the Visual Studio downloads page. Don't go on to the next section until this works. For more information about installing and troubleshooting Visual Studio, see Install Visual Studio.

Note

Depending on the version of Windows on the computer and the system security configuration, you might have to right-click to open the shortcut menu for the developer command prompt shortcut and then choose Run as Administrator to successfully build and run the program that you create by following this walkthrough.

Create a C source file and compile it on the command line

  1. In the developer command prompt window, enter cd c: to change the current working directory to the root of your C: drive. Next, enter md c:simple to create a directory, and then enter cd c:simple to change to that directory. This directory will hold your source file and the compiled program.

  2. Enter notepad simple.c at the developer command prompt. In the Notepad alert dialog that pops up, choose Yes to create a new simple.c file in your working directory.

  3. In Notepad, enter the following lines of code:

  4. On the Notepad menu bar, choose File > Save to save simple.c in your working directory.

  5. Switch back to the developer command prompt window. Enter dir at the command prompt to list the contents of the c:simple directory. You should see the source file simple.c in the directory listing, which looks something like:

    The dates and other details will differ on your computer. If you don't see your source code file, simple.c, make sure you've changed to the c:simple directory you created, and in Notepad, make sure that you saved your source file in this directory. Also make sure that you saved the source code with a .c file name extension, not a .txt extension.

  6. To compile your program, enter cl simple.c at the developer command prompt.

    You can see the executable program name, simple.exe, in the lines of output information that the compiler displays:

    Note

    If you get an error such as 'cl' is not recognized as an internal or external command, operable program or batch file,' error C1034, or error LNK1104, your developer command prompt is not set up correctly. For information on how to fix this issue, go back to the Open a developer command prompt section.

    Note

    If you get a different compiler or linker error or warning, review your source code to correct any errors, then save it and run the compiler again. For information about specific errors, use the search box at the top of this page to look for the error number.

  7. To run your program, enter simple at the command prompt.

    The program displays this text and then exits:

    Congratulations, you've compiled and run a C program by using the command line.

Next steps

This 'Hello, World' example is about as simple as a C program can get. Real world programs have header files and more source files, link in libraries, and do useful work.

You can use the steps in this walkthrough to build your own C code instead of typing the sample code shown. You can also build many C code sample programs that you find elsewhere. To compile a program that has additional source code files, enter them all on the command line, like:

cl file1.c file2.c file3.c

The compiler outputs a program called file1.exe. To change the name to program1.exe, add an /out linker option:

cl file1.c file2.c file3.c /link /out:program1.exe

And to catch more programming mistakes automatically, we recommend you compile by using either the /W3 or /W4 warning level option:

cl /W4 file1.c file2.c file3.c /link /out:program1.exe

The compiler, cl.exe, has many more options you can apply to build, optimize, debug, and analyze your code. For a quick list, enter cl /? at the developer command prompt. You can also compile and link separately and apply linker options in more complex build scenarios. For more information on compiler and linker options and usage, see C/C++ Building Reference.

You can use NMAKE and makefiles, or MSBuild and project files to configure and build more complex projects on the command line. For more information on using these tools, see NMAKE Reference and MSBuild.

The C and C++ languages are similar, but not the same. The Microsoft C/C++ compiler (MSVC) uses a simple rule to determine which language to use when it compiles your code. By default, the MSVC compiler treats all files that end in .c as C source code, and all files that end in .cpp as C++ source code. To force the compiler to treat all files as C non-dependent of file name extension, use the /Tc compiler option.

MSVC is compatible with the ISO C99 standard, but not strictly compliant. In most cases, portable C code will compile and run as expected. Visual C++ doesn't support most of the changes in ISO C11. Certain library functions and POSIX function names are deprecated by MSVC. The functions are supported, but the preferred names have changed. For more information, see Security Features in the CRT and Compiler Warning (level 3) C4996.

See also

Walkthrough: Creating a Standard C++ Program (C++)
C Language Reference
Projects and build systems
Compatibility

C++ (pronounced 'see-plus-plus') is an object oriented, general purpose programming language that was created in 1983 by Bjarne Stroustrup. It's used mainly for desktop software and game development, and is an extremely useful programming language to know.

So to start C++ programming, you'll need some way to write your C++ code, and then also a compiler which turns that code into something that your computer can directly read (often called 'machine language'). If you're using the Mac OS X operating system or a Linux distribution, I'd recommend using any text editor of your choice to write your code (I particularly like Sublime Text 2), and then using the 'g++' compiler to compile your code via the Terminal. For (Mac) OS X, g++ can be very easily installed as it comes bundled along with XCode.

Another popular choice for C++ coding and compilation is using an Integrated Development Environment (IDE) in which you can write and compile your code. For OS X you might want to use XCode if you're feeling worried about the g++ route (g++ can be a little complicated), and if you're using Windows, popular IDEs include Code::Blocks, which I personally recommend however does require some setup at the start (you may need to do some research), and Visual C++ Express, which is much easier to set up, however will require some sort of application pausing before the end of the 'main' function in most cases as it generates a window which will disappear after execution. If you decide to go with Visual C++ Express, just keep this in mind -- you may wish to put the system('PAUSE'); or _getch(); lines before the end of your 'main' function (the latter of which requires you to #include <conio.h>) -- if you don't understand what this means, you will soon enough.

How to use dev c++ compiler

Sample C Program In Dev C Online

So by this point, you should have your development environment properly set up (even if you don't entirely know how to use it yet). If you're using an IDE, create a new C++ project, often called a 'console project', and remove any code/text which is generated for you, and if you're using a separate text editor and compiler, just create a new file with the '.cpp' extension (the file extension for C++ source files) - I'm going to name mine 'project.cpp'.

To start off with, we're just going to add what's called a 'comment' to the top of our file which says that we've written the program. Comments are simply notes that you write (to either yourself, your team, or whoever else might see the code) that the C++ compiler completely ignores, and so these don't affect how your application actually runs. We can do single-line comments in C++ by using a double slash (//) and multi-line comments using /* to start the comment, and */ to end the comment. Take, for example, the following:

After a comment on your top line (which isn't entirely necessary), we need to 'include' a few things before we begin writing our main application logic. When we 'include' things in C++, we're simply taking pieces of pre-written code from a file - as such, includes are usually done at the start of a section of code so that the functionality can be used in the rest of the code. In this case we want to include the 'iostream' file (which stands for input output stream) so we can output and take in basic text data. These includes always start with a hash symbol (#), and then use the include keyword followed by the name of the file we wish to include (which we specify, in this case, in angle brackets):

As alluded to earlier, the stuff inside 'iostream' is for inputting and outputting text. The two most well-known things in here are called cout and cin (pronounced 'see-out' and 'see-in'), which are for outputting data and getting data from the user. These both, however, require the 'std' namespace - I'm not going to go into great detail about namespaces right now, but essentially just think about different namespaces as different drawers. A lot of the core C++ standard stuff is in the 'std' drawer and we can specify this by either writing std:: before every time we write cout, cin, and other things which require it, or for our simple purposes here, we can just use the namespace throughout out whole document. This is done by writing the using keyword, followed by the namespace keyword, followed by the namespace name, in this case, std:

Sample C Program In Dev C Pdf

Notice that I also finished the line by using a semicolon (;) - lines are often finished with a semicolon in C++ to show that the instruction or the line has finished. In this case, we're telling the compiler that we're done specifying the namespace by writing the semicolon.

With the top part of our document setup, we can actually begin writing our program's point of entry. All basic C++ programs start at what is called the 'main' function. A function is just a piece of code with a name, and that name, in this case, is 'main'. Functions also have a type, generally speaking the 'main' function should have the integer (whole number) type, and this is shown by writing the int keyword before the function name. This function type means that inside the function we must have a line which returns an integer value - don't worry too much about what this means right now, but if we return '0' from main, it generally means that we did everything without any errors. After we've written the function's name, we have to specify some brackets (which some people populate with some things, but we're going to leave them empty), and then some curly brackets which will actually contain our main application code. For now, I'm just going to put a comment in there. Our code so far should look as follows:

Notice that I put a tab-space before the comment - this is because the comment is inside the 'main' function and I wanted to visually show this. Indented code isn't necessary for your code to compile and run correctly, however it makes finding errors a hell of a lot easier, and if you don't do it, nobody will like you (or want to work with you!).

While we're talking about the 'main' function itself, let's put in that 'return' line we talked about earlier so that our main function abides to its type. This is done by simply writing the return keyword followed by the value which you want to return, followed by a semicolon - so in this case, return 0;. This will actually stop our 'main' function's execution though, so we want it to be the very last line of the function:

From here, we're going to complete our basic program by simply getting it to output 'Hello World!' (or text of your choice) to the screen. As alluded to earlier, this is done by using cout (which, remember, is in the std namespace). We can output a combination of different letters, numbers, and symbols, known as a string, by writing the cout keyword, followed by insertion operators, <<, followed by our string which is represented by wrapping in double quotes. We also need a semicolon to end the line.

The way cout works, is essentially that you can just put insertion operators after each piece of data you want to output to output some more. Numbers don't have to be surrounded in double quotes to be processed in the correct way be the compiler, so if we wanted to output a number after our 'Hello World!' piece of text, we could either put it inside our string, which would encapsulate the data, or we could put it after another set of insertion operators (and move the semicolon to the 'new' end of the line):

You should try to get used to this functionality. Without looking at the snippet below which reveals the answer, try to create a basic cout which would output a sentence with a number in the middle.

Dev C++ Compiler

We can add newlines to this output by either writing a backslash followed by the letter 'n' in a string (remember that strings are encapsulated by double quotes), or by using the endl keyword after some insertion operators. So our final piece of code which we're going to compile and run (which I've commented a bit to make it easier to understand), is as follows:

Sample C Program In Dev C 5

To compile and run the code in an IDE, you can usually just hit a conveniently placed 'Run' or 'Debug' button (Key shortcuts of F8 in Code::Blocks, F5 in Visual C++ Express, and +R in XCode), however the process of compiling and running is slightly more confusing when you have a separate text editor and compiler. If this is the case, save the file with the code we've written (and with the '.cpp' file extension, so call it something like 'project.cpp'), and then open up a Terminal window (if you don't know how to do this in your OS, Google it). You can then navigate to wherever your project file (i.e. 'project.cpp') is stored using the 'cd' command (again, you'll have to Google if you don't know how to do this), and then run some compilation and running commands which are compiler and OS-specific. If you're using g++, you can run g++ -o project project.cpp to compile the code in 'project.cpp' to a file named 'project', and then on OS X and Linux you can run ./project to run the generated 'project' file (and hence the program) itself.

In future tutorials I will expect you to know how to compile and run code in your own development environment, so it'd probably be a good idea for you to create a few C++ projects and compile/run them to get used to your development environment. As a little challenge to tie off the information in this tutorial (which will, of course, be built upon in future tutorials), try writing another cout line after the one we've already written that outputs something else.