We have had numerous reports of Apache dumping core when compiled with HP's ANSI C compiler using optimization. Disabling the compiler optimization has fixed these problems.

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..

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.

By using the ulimit command in bash, the limit command in tcsh, or the rlimit command in ksh. See the appropriate manual page for details. If you wish to enable or disable core dumping for all processes by default, you can change the default setting in linux/sched.h. Refer to definition of INIT_TASK, and look also in linux/resource.h. PAM support optimizes the system's environment, including the amount of memory a user is allowed.

Byte Craft Limited compilers have not been certified as ANSI-compliant, and we do not advertise compliance. However, we have used the ANSI C specification in developing our C compilers since the draft standard was first made available, and we continue to participate in software standards discussions via the Standards Council of Canada. Most ANSI C conforming programs can be compiled by our compilers.

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.

Let's assume that you already have a C++ library add_cpp.lib that was created inside the Microsoft Visual C++ workspace. This add_cpp.lib library contains a function float add_cpp(float a,float b) that you wish to use inside a Gedae function box. Follow these steps to access the function in your box: Write a new C++ file that provides a wrapper function for add_cpp() that exports the function to C using the extern "C" construct. In this example, create a file add_c.

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.

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;

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.

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.

In basic sonic terms, these transformers offer the very best depth and resolution, smoothly over the full audio range. For a more technical discussion, click here to read an Audio Note technical article on this very subject.

Check to see if a structure type declaration just before main() is missing its trailing semicolon, causing main() to be declared as returning a structure. See also questions 10.9 and 16.4.

Make sure you add mod_ssl to the Apache source tree first and then do a fresh configuration and installation of PHP3. For SSL support EAPI patches are required which have to change internal Apache structures. PHP3 needs to know about these in order to work correctly. Always make sure that -DEAPI is contained in the compiler flags when PHP3 is built.

A missing semicolon causes the compiler to believe that main returns a structure.  (The connection is hard to see because of the intervening comment.)  Since struct-valued functions are usually implemented by adding a hidden return pointer, the generated code for main() tries to accept three arguments, although only two are passed (in this case, by the C start-up code).  See also question 17.21.

Since it's hard to tell from a stack trace only, what is going wrong, please send as much information as possible. If you're lucky, you're the writer of the service and you can send the component implementation code and the code which instantiates the object as well. If you are not the component developer then you're forced to contact the component developer.

Anyone can use Dublin core metadata to describe the resources of an information system. Web pages are one of the most common types of resources to utilize the Dublin Core's descriptions, usually within HTML's meta tags however increasingly there are many digital archives of physical objects that are starting to make use of the Dublin Core.

In 1983, the American National Standards Institute (ANSI) commissioned a committee to standardize the C language. Their work was ratified as ANS X3.159-1989, and has since been adopted as ISO/IEC 9899:1990, and later amended.

Two available packages are ''defunc,'' posted to comp.sources.misc in December, 1993 (V41 i32,33), to alt.sources in January, 1994, and available from sunsite.unc.edu in pub/packages/development/libraries/defunc-1.3.tar.Z, and ''parse,'' at lamont.ldgo.columbia.edu. Other options include the S-Lang interpreter, available via anonymous ftp from amy.tch.harvard.edu in pub/slang, and the shareware Cmm (''C-minus-minus'' or ''C minus the hard stuff''). See also questions 18.16 and 20.6.