compiler vs interpreter?
87841
Hammer vs. Screwdriver?    Depends on what you're doing.\n\nIf you're simulating protein folding while investigating\nnew medicines, you probably want to compile your code in\norder to get maximum efficiency.  In that case, you don't\nmind messing around with compiler options and having to\nkeep track of a separate executable file.\n\nIf you want a simple utility that will run occasionally\nand clean up some files, why not just use a korn shell\nscript which is interpretted?  Only one file to keep\ntrack of (which is both "source" and "executable"), \nno compiler to mess with, no options to tweak, typically\neasier to debug and really no performance downside\n(since the work is  small enough that it appears to\nrun instantaneously anyway).\n\nEach has its own place.
159988
If J2EE was as bad as you think it is, why is it so widely used? Answer: it's not.\n\nIt's been a very long time since this technology could be accused of being generally inefficient. JIT and adaptive in-time compilers can actually recompile byte-code into assembley during runtime depending on how it's currently being used. This can produce faster execution in certain cases than C or C++.\n\nMost of the pain comes from starting the runtime, in an enterprise environment this is not an issue.\n\nPS. Remember it's just a specification. If you want to do Java just like C# (ie. compiled and ready to go as a binary), take a look at http://gcc.gnu.org/java/
524161
Dev-C++ is free and easy. It comes with the Mingw compiler. Download it at sourceforge.net: http://prdownloads.sourceforge.net/dev-cpp/devcpp-4.9.9.2_setup.exe
409704
I may not have written many programs in Java, but that sure as hell doesn't look like Java to me.\n\nEdit: It's actually C as you can see from the includes:\n#include<stdio.h>\n#include<conio.h>\n#include<math.h>\n#include<stdlib.h>\n\nC++ doesn't use <something.h> it just uses plain <something>.
1007930
Well, the compiler and linker should have built an *.exe file with the name of your program/project.  Just run it from the start / run option in the task bar.  Or click on it.  I hope that this is what you meant, your question is a little difficult for me to understand.
592030
source code-> MSIL-> Native cose through compilers
794890
language should have never been used for specifying JS vs VB or setting versions.\n\ntype is correct... language worked, but does not validate and is just OLD!
398955
Java and C++ are remarkably similar in terms of syntax.  Java has all of the same constructs that you are familiar with: for loops, while loops, pre- and post-increment, if-then-else, etc.  So you should be able to pick up the syntax pretty quickly.\n\nThe differences between Java and C++ have more to do with structure than syntax: the way that files are arranged, the way that code is compiled and run, the way that rules are enforced, and the things that come with the package.\n\nWith Java, there is just one file to describe a class, with the interface and the implementation together in the same file.  In C++ these parts are split into a header (.h) file and an implementation (.cpp) file.  This makes things simpler, in that with Java there are half as many files to manage.  It also makes it impossible to lose half of your class, as you can in C++ by losing either the .h or the .cpp file.  It also makes your code more open: if you want to show someone your interface (API) code, then they can also see your implementation.  There is a workaround for this, however, in that you can use the Java-Doc comments to automatically generate HTML-based documentation for your code that only describes your public API.  (Another nice difference –- automatic documentation!)\n\nJava source code is compiled to .class bytecode files.  These files are then run by the Java interpreter/JVM.  This adds an extra layer between your code and the OS, but surprisingly causes very little deterioration in performance, mostly due to really smart JVMs.  This buys you two things: portability and safety.  The portability comes from the fact that code is written to the JVM, which is an idealized stack-based virtual machine, and not to the quirks of the underlying OS.  This is what leads to the infamous “write once, run anywhere” claim.  The safety comes from the fact that all bytecode is checked at run time for any malicious or mal-formed code, and the JVM can restrict the access of any piece of code so that it can't get to sensitive stuff (like your personal files, or the microphone, for instance).\n\nSafety is the common heading for several other differences between Java and C++: there are no pointers in Java (at least not directly), so there are no dangling pointers, uninitialized pointers, or bizarre pointer math errors; arrays are dynamically checked for staying within the boundaries, so there are no out-of-bounds errors; you can't cast an variable to an incompatible type in Java, so data structures can't get corrupted in that way; exceptions must be caught (this check is done at compile time), so there are no uncaught exceptions to bring down your application; and the list goes on!\n\nThus far it might seem like Java is missing a lot of things that are found in C++.  So what would you probably miss if you made the move to Java?  Pointers, templates, operator overloading, multiple inheritance, and a preprocessor.  What wouldn't you miss?  Pointers, templates, operator overloading, multiple inheritance, and a preprocessor.  You might have noticed that these two lists are remarkably similar.  How can this be?  It is one of those things where you might miss some particular feature at first, and even wonder how in the world you will do without it, but once you are familiar with Java and the way that it works, you wonder why you ever bothered with that complicated stuff in the first place.  Java has elegant replacements for many of these missing items, or better yet, makes them completely unnecessary by design.  A good example is multiple inheritance – in Java there is only a single parent class for a given user-defined class, but a class can implement any number of interfaces, which are special classes that only specify methods and operations but have no implementation whatsoever.  A class that implements a given interface can be passed anywhere that the interface is expected, regardless of its size or the way that it is implemented.  It
27985
You can add a Perl parser into a C++ program.  Many games do something similar to this; writing the game engine in C++ and scripting the AI using Perl.
98474
you can use c compiler (cc)\ncc srcfile.c -o destfile
243412
Depending on the language you feel most comfortable with.\nFor Fortran, C, C++ I suggest GNU tools.\nJava you can download from Sun for free.\nAs IDE eclipse is available for free and you can plug in most commonly used compilers, many of these as well available without charge.
1131111
Are you including computer programming languages?  (Geek alert)
662885
No difference ,they are all used for dynamic allocation.only syntax difference i guess.
810227
Compilers. Of course, there is the simple matter of learning the programming language.\n\nHeres a free C++ compiler:\nhttp://www.bloodshed.net/dev/devcpp.html
400603
Those mentioned above (Visual studio) are fine but for beginning I'd recommend something smaller and simpler... try devC++... it's free and can be found at bloodshed.net...\n\nthen (just to keep the tradition) write something like this:\n#include<stdio.h>\nmain()\n{\nprintf("Hello World&#92;n");\ngetchar();\n}\nThen hit f9 to save the file, compile it and run...
822024
1). A compiler "compiles" a code so that the host Operating System can understand. It's generally speaking. The compiler doesn't interact directly with the hardware, this is the job for the Operating System!\n2). Yes. You can download as many compilers as you prefer. A compiler is a software which interacts with the operating system, just like any other..\n3). This is difficult to answer... The starting point for creating compilers are formal languages and theory of automata.. Then comes the implementation... \n4). C/C++ is the industry standard, so of course many software are written in this language (but not only in this one...). Libraries for grafic function include OpenGL (Glut,FreeGlut and so on), DirectX... Renedering software is also being used in the gaming industry. (let's not foret about Artficial Intelligence)\n5). You can update a compiler by downloading the improved version or adding extra libraries to it. You can even create your own libraries if you prefer to start from scratch.\n6). Unix for example is entirelly based on C language! C language doesn't support OOP (Object Orientation Programming), that's one of the reason C++ was created. It's hard to say in what language windows is written for example since it's closed source...
102450
A compiler is designed to take a language, then break it down into simple pieces, examine it for correctness and then generate the base assembly code for the processor on which it is developed.\n\nThe first stage of the compiler is tokenizing, or breaking down each of the letters the compiler reads into groups of 'words' that make sense to the compiler.  For example, the statement "int i = 10;" can be broken into 'int', 'i', '=', '10' and ';'.\n\nNext, lexical analysis is done to ensure that the tokens read by the compiler fit the language.  In the previous example, 'int' is seen as a keyword, 'i' recognized as a variable name, '=' as an operator, '10' as a literal constant, and ';' as a statement terminator.\n\nNow, the compiler performs semantical analysis in order to make sure that the tokens it recognizes are in proper order and that they make sense.  An example is a sentence like "going to the store are we", as opposed to "we are going to the store".  In the code example above, "int i = 10;" is semantically correct, wherease "int 10 i =;" is not, even though the tokens are valid.\n\nWhen the language is determined to be correct, the compiler goes into the "code generation" phase, which can consist of pseudo-code that is optimized, then converted into machine language that the computer can understand.\n\nIn a nutshell, language compilers usually understand the language by: a) breaking the language down into its individual 'pieces'; b) ensuring that all the pieces are in correct order according to the 'rules' of the language; and c) convert that language to the resulting native language of the machine.