We have finally merged in the past years boost-build changes into our branch and have run into the following issue with this change:

 

SHA-1: 290e284ffeef6ffccb5c05db69398c47cd0cf1ea

 

* topological sort ordered includes.

 

It appears that this line in handle-flag-value() is reversing the order of the includes (the order rule is doing it):

 

296:            result = [ $(order).order [ sequence.unique $(result) : stable ] ] ;

 

I hope this was not done on purpose since the change in behavior seems drastic as compared to what it was doing before.  In order to recover from this reversal, we are currently doing this:

 

296:            result = [ $(order).order [ sequence.reverse [ sequence.unique $(result) : stable ] ] ] ;

 

Is this an oversight? Can the original behavior be restored? Is there a better way for us to restore the functionality without incurring an additional traversal over the list?

 

Thanks,

 

Chris



CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient(s) and contain information that may be confidential and/or legally privileged. If you have received this email in error, please notify the sender by reply email and delete the message. Any disclosure, copying, distribution or use of this communication (including attachments) by someone other than the intended recipient is prohibited. Thank you.