aboutsummaryrefslogtreecommitdiff
path: root/gold/testsuite/script_test_9.cc
diff options
context:
space:
mode:
authorTom Tromey <tom@tromey.com>2025-03-20 09:44:59 -0600
committerTom Tromey <tom@tromey.com>2025-03-21 09:27:32 -0600
commit70c0de234fc6d8b349bf0fab35f957b16c679678 (patch)
tree80a1516a3cdc36740d7a77f78f7b53c57787217f /gold/testsuite/script_test_9.cc
parenta6bc5efb91236fe632b0ca329dc1f0123036262d (diff)
downloadbinutils-70c0de234fc6d8b349bf0fab35f957b16c679678.zip
binutils-70c0de234fc6d8b349bf0fab35f957b16c679678.tar.gz
binutils-70c0de234fc6d8b349bf0fab35f957b16c679678.tar.bz2
Rename die_info::sibling to die_info::next
I want to add support for C++ foreach iteration over DIE siblings. I considered writing a custom iterator for this, but it would be largely identical to the already-existing next_iterator. I didn't want to duplicate the code... Then I tried parameterizing next_iterator by having it take an optional pointer-to-member template argument. However, this would involve changes in many places, because currently a next_iterator can be instantiated before the underlying type is complete. So in the end I decided to rename die_info::sibling to die_info::next. This name is slightly worse but (1) IMO it isn't really all that bad, nobody would have blinked if it was called 'next' in the initial patch, and (2) with the change to iteration it is barely used. Approved-By: Simon Marchi <simon.marchi@efficios.com>
Diffstat (limited to 'gold/testsuite/script_test_9.cc')
0 files changed, 0 insertions, 0 deletions