Had a bug in order I was processing include dependencies.
Example of bug:

Consider the following files with dependencies.

main.rph includes a.rph and then b.rph

a.rph includes c.rph.
b.rph includes a.rph.

Order for dependency resolution should then be c.rph, a/b.rph,
main.rph.  Previous algorithm had a bug.  It would correctly label
that c.rph should be included before a.rph on first pass.  However,
when it encountered that b.rph depended on a.rph as well, it would
increase priority of including a.rph without also then increasing
priority of including c.rph.  In this way, a.rph might be included
*before* c.rph and break things.