I did this once long ago in C. Nibble through your file
char by char and change state at the appropriate events. You need to track states like: directive, code, comment, comment_plus, string_literal, char_literal, directive_string, and directive_angle_string (system lib names). You also need to track if you are at the start_of_line, and would need to look ahead a char on occasion and deal with escapes.
As I recall the compilation sequence of trigraphs, preprocessing, and processing did not have any real
impact. I just bailed on trigraphs; I have still never seen
a live one. Trigraphs may
be non-events for your purpose, I had not considered that
on my first go-round.
The Right-Thing is to replace a comment with a single space.
Be well,
rir
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
|
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.