[[cpphs @ 2005-04-15 16:06:40 by malcolm] malcolm**20050415160653 Documentation updates. ] { hunk ./CHANGELOG 1 +Version 1.0 +----------- + * Add a compatibility script cpphs.compat, allowing cpphs to act as + a drop-in replacement for cpp, e.g. + ghc -cpp -pgmP cpphs.compat + * Place quotes around replacements for special macros __FILE__, __DATE__, + and __TIME__. + * If no files are specified, read from stdin. + hunk ./README 21 +If you want to use cpphs as a completely drop-in replacement for the +real cpp, that is, to accept the same arguments, and have broadly +the same behaviour in response to them, then edit the "cpphs.compat" +script to point to the installed location of cpphs, then use this +script instead of cpp, e.g. + ghc -cpp -pgmP cpphs.compat + hunk ./docs/index.html 119 -You can give any number of filenames on the command-line. The results -are catenated on standard output. (Macro definitions in one file do -not carry over into the next.) +You can give any number of filenames on the command-line. If no +filename is given, cpphs reads from standard input. The results are +catenated on standard output. (Macro definitions in one file do not +carry over into the next.) hunk ./docs/index.html 131 +
hunk ./docs/index.html 315 + + +
+You will notice that the command-line arguments for cpphs +are not the same as for the original cpp. If you want +to use cpphs as a completely drop-in replacement for +the real cpp, that is, to accept the same arguments, and +have broadly the same behaviour in response to them, then edit the +cpphs.compat script to point to the installed location of +cpphs, then use this script instead of cpp, e.g. +
+ ghc -cpp -pgmP cpphs.compat }