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.

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.

Probably you are using the wrong C compiler. Grex has two compilers installed. cc is only used for building certain system executables. It is not ANSI standard, and it lacks certain standard include files. You need to use gcc instead. This is a fairly recent version of the Gnu C compiler. It is ANSI standard and very complete.

For the "B" part (including the version in which you also return the pair of points along with the distance), you are expected to put your divide-and-conquer algorithm in a file called "closest-pair.cc" You will also need to modify lab1b.cc as indicated. A makefile is included with the provided code. Copy that into the directory with the rest of the code. Then just type "make". After successfull compilation and linking there will be a file called "lab1b.out". Just type "lab1b.out" to run it.

You should use the Compaq compiler fort to compile both your fortran 77 and fortran 90 programs. C and C++ programs can be compiled with gcc or g++, respecively. To compile and link your MPI programs to the MPI libraries, use mpif77, mpif90, or mpicc. The mpi scripts use fort to compile and link your fortran MPI programs, and gcc or g++ to compile and link your MPI C or C++ programs. You can compile your codes on any machine, and you do not need to submit a job to compile your codes.

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.

From: libes (Don Libes) To: wren@io.nosc.mil Subject: Compile fails with: Don't know how to make pty_.c > I'm trying to compile Expect on hpux 9.01, > downloaded from ftp.cme.nist.gov expect.tar > after running config > the make fails with "Don't know how to make pty_.c. (compile fails) > I see three versions pty_sgttyb.c, pty_termios.c and pty_unicos.c in > the load, but the configure picked none of them. > I tried forcing to pty_termios.

Have a look at the install readme file that comes along with Xvid. It describes how to use the Xvid build scripts to compile Xvid with gcc under Linux or MinGW/CygWin. Xvid can also be compiled with Microsoft Visual C++ compiler using the provided project files included in the build directory. For other compilers you're pretty much on your own. It should be not very difficult however to make the code compile with a different compiler.

Almost any program with symbols can be probed. The "full support" described below is based on the debug information needed for source lines and target expressions. Support for additional architectures, operating systems and compilers is always in progress, so please contact if you don't see what you need here. Aprobe supports the Microsoft Visual C++ development system versions 6 and 7 but does not support .NET (Dynamic Runtime Model) applications.

Opennap NG's current codebase is written in ISO C99. Unfortunately, most commercial C compilers do not (or not fully) support ISO C99 but rather define their own, proprietary and non-portable language extensions. GCC (GNU Compiler Collection) fully supports ISO C99. As it also makes some use of features unique to GCC, such as platform-dependent inline assembly, Opennap NG requires GCC as compiler.

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.

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.

Octave is a high-level interactive language, primarily intended for numerical computations that is mostly compatible with MATLAB.(1) Octave can do arithmetic for real and complex scalars and matrices, solve sets of nonlinear algebraic equations, integrate functions over finite and infinite intervals, and integrate systems of ordinary differential and differential-algebraic equations. Octave uses the GNU readline library to handle reading and editing input.

There are two ways. One is to use the program g++ instead of gcc when you compile. g++ is the same as gcc except that it sends options to the sub programs that actually do the work which work with C++. The other way is to add the option -lstdc++ to the command line. This tells gcc to link with the standard C++ library. I prefer using g++ because it knows more about properly compiling for C++ than I do.

Borland users have been finding that it's impossible to compile the LEX and YACC-generated parser files in PROLOGIO from wxWindows 1.50. PROLOGIO is required for compiling wxBuilder. Peter Trattler and Edward Zimmermann have improved PROLOGIO to allow FLEX to be optionally used instead of LEX; see the PROLOGIO manual for more details. If you have FLEX (the default Linux lexical analyser generator), you can generate a lex_yy.c which compiles more cleanly. In release 1.

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.