header-files

Whenever I compile my program, I get the error above. Amit If you have problems like that, first of all your TC folder put in to the C:..drive. after completing installation open turbo c blue screen. there is a OPTIONS > Directories ..in that you can see for option to set up path.. include directories..you can set path there now.. C:\TC\INCUDE libraries Directories..you can set path there... C:\TC\LIB if you want to store your output in BIN then you can set.. C:\TC\BIN ..otherwise you can set another path where you want to store your output.. Finally you can give OK and finished processes.. It

While answering this question I compiled the code on Ideone and got this error implicit declaration of function ‘scanf_s’ [-Wimplicit-function-declaration] Isn't stdio.h is the header for scanf_s ? scanf_s is Microsoft-specific. Header is stdio.h but not in GCC. Used to Read formatted data from the standard input stream. These versions of scanf, scanf_s, _scanf_l, wscanf, _wscanf_l have security enhancements Where as Ideone uses GCC because of this only you got undefined reference to scanf_s Mostly You can found this function in windows based compilers like Visual Studio 2008 and Microsoft

I'm trying to learn about string s, but different sources tell my to include different headers. Some say to use <string.h> , but others mention "apstring.h" . I was able to do some basic stuff with apstring , but I've been told the other one is more powerful. When I include <string.h> and try to declare some string variables, however, I get errors. What is the proper usage? GManNickG You want to include <string> and use std::string : #include <string> #include <iostream> int main() { std::string s = "a string"; std::cout << s << std::endl; } But what you really need to do is get an

Are there any tools that help organizing the #include s that belong at the top of a .c or .h file? I was just wondering because I am reorganizing my code, moving various small function definitions/declarations from one long file into different smaller files. Now each of the smaller files needs a subset of the #include s that were at the top of the long file. It's just annoying and error-prone to figure out all #includes by hand. Often the code compiles even though not all #include s are there. Example: File A uses std::vector extensively but doesn't include vector ; but it currently includes

I can define the body of a class constructor in the class .h file or in the implementation file .cpp . These two styles are probably identical as far as the compiler is concerned within a specific project (project for me means DLL ). Same applies to any member functions really: they can be defined in the header file or just declared there and then defined in the cpp file. However, I found that if I need to include such class header file(s) in different projects (meaning that ultimately the code that uses the header file ends up in a different DLL ) then having the actual implementation in the