Tough problem. You could try a queue - the idea is to store those keys whose values are not complete, and keep substituting until they are complete: 
use strict;
use Data::Dumper;

my (%hash,@queue);

while (<DATA>) {
   chomp;
   if (/^#DEFINE\s+<([^>]+)>\s+(.*)/) {
      $hash{$1} = $2;
   }
}

do_it($_) for keys %hash;
do_it(shift @queue) while @queue;

sub do_it {
   my $key = shift;
   $hash{$key} =~ s/<([^>]+)>/$hash{$1}/g;
   unshift @queue, $key if $hash{$key} =~ /</;
}

print Dumper \%hash;

__DATA__
------------------
#DEFINE <PATH> /path/to/something
#DEFINE <VERSION> v12<REV>
#DEFINE <REV> 3
#DEFINE <FILE> <PATH>/foo_<VERSION>.txt

[download]
BUT!!! This is going to loop infinitely if you have one single circular reference in your #DEFINE statements. For example, change <VERSION> to: 
#DEFINE <VERSION> v12<REV><FILE>

[download]
and this will not work. Hopefully someone else will have a better answer, but if you are %110 certain that this will not be the case, then this code will prevent unecessary iterations.

p.s. this might be a job for Parse::RecDescent ...

UPDATE: danger++ and sfink++

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

In reply to (jeffa) Re: Parse C-like define statements by jeffa
in thread Parse C-like define statements by Cirollo

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.