This is certainly not an easy problem. It's easy to write a piece
of code that will only terminate because it has exhausted all memory,
or ran out of stack space - because you can have loops. Furthermore,
even if there aren't loops, a naive approach might lead to a program
that runs in time quadratic to the number of defines.
I suggest approaching the problem as seeing the file as a graph.
Each #define is a node, with as (outgoing) edges
edges to nodes its definition is refering to.
Now that you have made a graph, first you need to find out whether there
are any loops - if there are, determine what you are going to do with
them. Throw them out, die(), whatever. Second, do a topological sort,
then you can process the defines like you are doing now:
$defines{$_} =~ s/<(\w+)>/$defines{$1}/g;
Luckely, there's a graph module on CPAN that could help you.
Abigail
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.