Does the Standard specify how a source file needs to be compiled and would an extra preprocessing step be non-Standard?

I don't have a copy of the standard here (long time ago read some portions of the draft though), but I'm quite sure the standard doesn't even dictate sources have to be present as files. If I remember correctly, a long time back (in the 90s) IBM's Visual Age C++ IDE tried to abandon storing sources in files altogether Since the C++-standard says nothing about the build system (make, jam, or whatsoever), everything that comes before the compiler (and the C++ preprocessor) is outside the scope of the standard. So, something like moc or generation of config.

H is non-standard with regard to the C++-standard, and is not disallowed either But there are other standards as well. For example, for Qt using moc is the "standard" for preprocessing files before invoking the C++ compiler, just as in linux development using autoconf, GNU make and other tools is.

I don't have a copy of the standard here (long time ago read some portions of the draft though), but I'm quite sure the standard doesn't even dictate sources have to be present as files. If I remember correctly, a long time back (in the 90s) IBM's Visual Age C++ IDE tried to abandon storing sources in files altogether. Since the C++-standard says nothing about the build system (make, jam, or whatsoever), everything that comes before the compiler (and the C++ preprocessor) is outside the scope of the standard.So, something like moc or generation of config.

H is non-standard with regard to the C++-standard, and is not disallowed either. But there are other standards as well. For example, for Qt using moc is the "standard" for preprocessing files before invoking the C++ compiler, just as in linux development using autoconf, GNU make and other tools is.

Sounds reasonable to me. If I write a Java-to-C++ compiler that takes in Java source and outputs C++ source, then the C++ standard couldn't care less provided that what I output is valid C++. But clearly what I've written is a Java compiler, it's not a C++ compiler.

Likewise moc is a "Qt-C++ compiler" (or part of one), not a C++ compiler. The difference is just that the input to moc is much closer to standard C++ than is the input to my Java compiler. – Steve Jessop Mar 8 at 18:17.

I don't have a copy of the standard here (long time ago read some portions of the draft though), but I'm quite sure the standard doesn't even dictate sources have to be present as files. If I remember correctly, a long time back (in the 90s) IBM's Visual Age C++ IDE tried to abandon storing sources in files altogether.

Gcc.gnu.org/onlinedocs/gcc/Overall-Options.html‎CachedSimilarCompilation can involve up to four stages: preprocessing, compilation proper, ... object files (those newly compiled, and those specified as input) into an executable file. Ii: C++ source code that should not be preprocessed. .... -v: Print (on standard error output) the commands executed to run the stages of compilation.

Gcc.gnu.org/onlinedocs/gcc/Preprocessor-Options.html‎CachedSimilarParentheses are meaningful to most shells, so you will need to quote the option. ... If the directory dir is a standard system include directory, the option is ignored to ensure that ... This is the same as specifying file as the second non-option argument to cpp . Gcc has a ... Source code which triggers warnings will be rejected.

Tigcc.ticalc.org/doc/comopts.html‎CachedSimilarFor more info about standard options that are recognized by the compiler, read the official manual. ... If you want to use the IDE instead, you do not need to worry about these topics. ... Compile or assemble the source files, but do not link.

En.wikibooks.org/wiki/C_Programming/Preprocessor‎CachedSimilarA list of standard C header files is listed below in the Headers table. ... the preprocessor is expected to search in some additional, usually user-defined, ... You should check the software implementation of the C standard you intend on ... The compiler does not know anything about the macros and never gets to see them. Publib.boulder.ibm.com/infocenter/comphelp/...ibm.../gs_cmplnk.htm‎CachedSimilarTo see the compiler step through these phases, specify the -qphsinfo and -v ... file or the -qsourcetype compiler option define additional non-standard filename suffixes.

Www.freebsd.org/doc/en/books/developers.../tools-compiling.html‎CachedSimilarPre-process your source code to remove comments and do other tricks like ... Sometimes step 1 is referred to as pre-processing and steps 3-4 as assembling. ... If you have more than one file to compile, just do something like ... Despite the name, it does not guarantee strictly that your code will comply to the standard. Herbert.the-little-red-haired-girl.org/html/gcc/cpp_1.html‎CachedSimilarThe standard way to do this is to enclose the entire real contents of the file in a conditional, like this: ... In a user header file, the macro name should not begin with `_' .

Www.cs.utah.edu/dept/old/texinfo/cpp/cpp... a header file produces the same results in C compilation as copying the .... The standard way to do this is to enclose the entire real contents of the file in a conditional, like this: ... `#pragma once' is now obsolete and should not be used at all. Stackoverflow.com/.../does-the-standard-... gcc program accepts options and file names as operands. ... When you invoke GCC , it normally does preprocessing, compilation, ... If the description for a particular option does not mention a source language, you can use that option with all ...... By specifying a base standard, the compiler will accept all programs ...

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.

Related Questions

» About WebKnox
» Contact
» WebKnox Blog
» RSS
» Newsletter
» Twitter
» API
» API Showcase