Most Modula-2 compilers are written in Modula-2. It seems rather strange to me that one would want to trust the compilation of a good language to a tool written in a poor one.

C++ is a superset of something, we're not sure what. You can use a C++ compiler to compile C code, but the results may surprise you.

The source code for a Java program is also known as a compilation unit, which contains the code for a top level Java class or interface. A Java compilation unit is usually created in the form of a file with a .java extension and is passed to the compiler as a file path reference. The Java source file naming convention is not a standard specified by the Java language but is a common feature of Java compilers, such as javac, to help locate source code.

Where have you been? :-) Sun has dropped their old K&R C compiler, supposedly to create a market for multiple compiler suppliers to provide better performance and features. Here are some of the contenders: SunPro, SMCC, and various distributors sell a new ANSI-standard C compiler on the unbundled (extra cost) SPARCcompiler/SPARCworks CD-ROM. There are some other nice tools there too, like a "make tool" and a visual diff (interactive diff).

They've been programming more than ten years. You haven't. Draw your own conclusions. That's right! They hadn't noticed it. No doubt their compilers have it too, and its behavior is identical everywhere else in the world, also. That would explain everything.

already ported version for DOS+DJGPP can be found at ftp://ftp.uni-stuttgart.de/pub/unix/programming/modula/ Several of the compilers available work or can work by producing C or C++ code and can also serve this purpose. See p1, XDS and Ulm's m2c (not the same as mtc) listings for examples.

Not exactly; it can contain a pointer to another structure of the same type. Try: typedef struct { char *item; double *next; } NODEFAKE; typedef struct { char *item; NODEFAKE *next; } NODEPTR;

Sure. However, you will be responsible for making any needed modifications to the provided code. The provided IntervalTimer will not work on other platforms since it makes calls into the Unix operating system. You can replace this by whatever system utility you have to get the time. Then by getting the time before and after the algorithm runs you can take their difference to determine the elapsed time. Just be sure that your procedure is the only process running.

It depends. If your compiler is C99-compliant, then patches to support it are likely to be welcome if they do not pollute the source code with #ifdefs related to the compiler. Visual C++ is not compliant to the C standard and does not support the inline assembly used in FFmpeg. If you wish - for whatever weird reason - to use Visual C++ for your project then you can link the Visual C++ code with libav* as long as you compile the latter with a working C compiler.

OEChem distributions are generally labelled clearly to indicate the corresponding compiler and version. Additional compiler support information can be found at the OpenEye Platform Support document, in the accompanying technical notes.

MICRO-C is a "near ANSI" subset compiler. It does however, support more of the 'C' language than most other subset compilers, including: Micro-C has a long history, and began life as a K&R only compiler. It has evolved toward ANSI quite a bit, and continues to do so, however it is NOT a fully ANSI compliant compiler, and most likely never will be..

We, ( CodeGen, Inc.) sell a C-to-Fcode compiler. Well, it actually generates IEEE-1275 Forth that then must be run through a tokenizer. Really, it generates pretty ugly Forth code. It's easy to generate lousy Forth, but it's very difficult to generate nice clean optimized Forth. C and stack-based languages don't mix too well. I end up faking a C variable stack-frame using a Forth $frame variable for local vars. MPE has produced a C to stack-machine compiler.

The easiest way is to buy the distribution CD from the IEEE Student Branch ($5 for IEEE members, $10 for non). It contains the Cygwin (GNU) C++ compiler, the Insight debugger, the "Teaching Machine" and instructional videos. If you have a fast internet connection and don't want the videos etc., you can go to Cygwin's site and click on the "Install Now!" icon. Be sure to install at least the following packages:

Yes, but you should compile and run your test cases using the Cygwin/GNU compiler (g++) in the lab before you submit your assignments. If it works there, then it's ok. (Of course we may find test cases for which your program doesn't work on any compiler.) where files is a list of one or more files that the compiler is to compile, and options is one or more of the following. (There are others, these are just the most relevant ones.) Give all warnings.

I'm looking for new questions (with answers), better answers, or both. Please send suggestions to bug-octave@bevo.che.wisc.edu. If you have general questions about Octave, or need help for something that is not covered by the Octave manual or the FAQ, please use the help-octave@bevo.che.wisc.edu mailing list. This FAQ is intended to supplement, not replace, the Octave manual.

This is most likely due to attempting to build a console program as a GUI application. If you intended to create a console app, make a new project with the console wizard.

Modula-2 is a computing language, or more properly a computing notation. It was designed by Niklaus Wirth in the early 1980s as a replacement for Pascal. It is small, teachable, highly readable, structured, modular, and suitable for software engineering very large projects. ISO standard Modula-2 has block-level exceptions, module-level termination, a standard I/O and utility library, coroutines, object oriented extensions and generic facilities.

A1. Modula-2 is a type-safe language and its compilers will therefore catch many errors that otherwise show up only at run time. While professional programmers need to learn C++ because it is commonly used, it is important to begin a discipline of deliberate, engineered programming at the outset. Modula-2 is easier to write in, easier to read (it reads left to right) and easier to debug. It lends itself well to software engineering of very large projects.

There are many systems of indentation advocated, but all of them have the same basic flaw; they will mislead the reader when the actual code logic does not follow the indentation. It is better to avoid indentation entirely, so the reader will not be misled.

The following is a response from a developer on the C# compiler team: We get rid of unused locals (i.e., locals that are never read, even if assigned). We get rid of unreachable code. We get rid of try-catch with an empty try. We get rid of try-finally with an empty try. We get rid of try-finally with an empty finally.

I recommend Microsoft Visual C because it's the industry standard... and also what I use for current projects. I used to use Watcom C when it was the only 32-bit compiler. I had lots of trouble finding example code for it because it was not so popular. Thankfully, everything is 32-bit these days. You'll save yourself a lot of trouble in the future by starting with a popular compiler.

The compiler only works for a small subset of Basic and produces quite inefficient code. I do not recommend it.

Sun's "Studio" compiler suite can be obtained at http://www.sun.com/software/products/studio. Various third-party commercial SPARC compilers are also available, including: The open-source GCC compiler and related tools are available on the Solaris Software Companion CD, which is part of the media kit for the Solaris distribution. The contents of this CD are also available for free download at http://www.sun.

Yes. Alex Ramos has written a GNU C back end for the Saturn processor. Binaries are available for both Linux and Windows 95/NT, and source is available for compilation on other platforms.