 |
Filepp - Default branch
|
Section: Unix
|
|
|
|
| Added: Wed, Dec 6th 2000 18:28 UTC (7 years, 7 months ago) |
Updated: Wed, Mar 7th 2007 05:52 UTC (1 year, 4 months ago) |
|
|
About:
filepp is a generic file preprocessor designed to allow the functionality provided by the C preprocessor to be used with any file type. It supports the full set of C preprocessor keywords (#include, #define, #if, etc.). filepp is also highly customisable and allows users to easily add their own keywords or modify the behaviour of existing keywords.
Author:
Darren Miller [contact developer]
Homepage:
http://www.cabaret.demon.co.uk/filepp/
Tar/GZ:
http://www.cabaret.demon.co.uk/filepp/filepp-1.8.0.tar.gz
Changelog:
http://www.cabaret.demon.co.uk/filepp/ChangeLog
RPM package:
http://www.cabaret.demon.co.uk/filepp/filepp-1.8.0-1.noarch.rpm
Mirror site:
http://www-users.york.ac.uk/~dm26/filepp/
Trove categories:
[change]
Dependencies:
[change]
No dependencies filed
|
|
» Rating:
8.32/10.00
(Rank N/A)
» Vitality: 0.01% (Rank 3441)
» Popularity: 0.95% (Rank 6010)
 
(click to enlarge graphs)
Record hits: 13,414
URL hits: 3,852
Subscribers: 19
|
|
Branches
Comments
[»]
I don't understand
by Daniel Pearson - Feb 19th 2001 08:55:35
Why did someone feel the need to rewrite the C pre-processor? There's
nothing
preventing you from using the C pre-processor on files that aren't C
sources.
--
.signature: No such file or directory
[reply]
[top]
[»]
Re: I don't understand
by Darren Miller - Feb 19th 2001 17:25:09
> Why did someone feel the need to rewrite
> the C pre-processor? There's nothing
> preventing you from using the C
> pre-processor on files that aren't C
> sources.
>
cpp is designed specifically to generate output for the C compiler. Yes,
you can use any file type with it, but the output it creates includes loads
of blank lines and lines of the style:
# 1 "file.c"
Obviously these lines are very useful to the C compiler, but no use in say
an HTML file.
Also, as filepp is written in Perl, it is 8-bit clean and so works on any
character set, not just ASCII characters.
Filepp is also customisable and hopefully more user friendly than cpp.
[reply]
[top]
[»]
C-centricity
by mikpos - Feb 20th 2001 12:59:38
> % Why did someone feel the need to rewrite
> % the C pre-processor? There's nothing
> % preventing you from using the C
> % pre-processor on files that aren't C
> % sources.
> cpp is designed specifically to
> generate output for the C compiler.
> Yes, you can use any file type with it,
> but the output it creates includes loads
> of blank lines and lines of the style:
>
> # 1 "file.c"
>
> Obviously these lines are very useful
> to the C compiler, but no use in say an
> HTML file.
>
> Also, as filepp is written in Perl, it
> is 8-bit clean and so works on any
> character set, not just ASCII
> characters.
>
> Filepp is also customisable and
> hopefully more user friendly than cpp.
Also, I should point out that the C pre-processor is C-centric in other
ways. For example, something like:
#if 0
"
#endif
is illegal and would cause cpp to choke. Everything must be made up of
valid C pre-processor tokens, and " is not one of them (because it is an
unterminated string).
[reply]
[top]
[»]
Re: I don't understand
by pixelbeat - Mar 12th 2001 20:26:28
>
> % Why did someone feel the need to
> rewrite
> % the C pre-processor? There's
> nothing
> % preventing you from using the C
> % pre-processor on files that aren't
> C
> % sources.
> %
>
>
> cpp is designed specifically to
> generate output for the C compiler.
> Yes, you can use any file type with it,
> but the output it creates includes loads
> of blank lines and lines of the style:
>
> # 1 "file.c"
>
> Obviously these lines are very useful
> to the C compiler, but no use in say an
> HTML file.
>
> Also, as filepp is written in Perl, it
> is 8-bit clean and so works on any
> character set, not just ASCII
> characters.
>
> Filepp is also customisable and
> hopefully more user friendly than cpp.
>
If the output from cpp is not what's required,
why didn't you modify cpp slightly and provide
a switch to choose the new functionality, instead
of reinventing 95% of cpp again.
[reply]
[top]
[»]
Re: I don't understand
by Darren Miller - Mar 26th 2001 04:57:49
The short answer is Perl. I wanted to write a generic file preprocessor
which had a core set of keywords (same as cpp), but which was easy to
modify and extend by adding further keywords. As I wanted to write the new
keywords in Perl, it made sense to write it all in Perl.
[reply]
[top]
[»]
Re: I don't understand
by David Wolfe - Feb 7th 2002 11:52:11
> Why did someone feel the need to rewrite
> the C pre-processor?
CPP is not a good general-purpose macro processor.
The question is why would one reimplement m4?
E.g.
GNU m4.
[reply]
[top]
|
|
|
