[DynInst_API:] [dyninst/dyninst] 72cdbe: Deprecate Expression::getUses

[Tim Haines <noreply@xxxxxxxxxx>]

  Branch: refs/heads/thaines/deprecate_Expression_getUses
  Home:   https://github.com/dyninst/dyninst
  Commit: 72cdbe8d1fe5f8ed066810b087101d30ffc21e6f
      https://github.com/dyninst/dyninst/commit/72cdbe8d1fe5f8ed066810b087101d30ffc21e6f
  Author: Tim Haines <thaines.astro@xxxxxxxxx>
  Date:   2025-10-25 (Sat, 25 Oct 2025)

  Changed paths:
    M dataflowAPI/src/AbslocInterface.C
    M instructionAPI/h/BinaryFunction.h
    M instructionAPI/h/Dereference.h
    M instructionAPI/h/Expression.h
    M instructionAPI/h/Immediate.h
    M instructionAPI/h/InstructionAST.h
    M instructionAPI/h/MultiRegister.h
    M instructionAPI/h/Ternary.h
    M instructionAPI/src/Immediate.C
    M instructionAPI/src/Operand.C
    M patchAPI/src/PatchBlock.C

  Log Message:
  -----------
  Deprecate Expression::getUses

Having in-out parameters makes callsites clunky- particularly for
range-base for loops. The name is also unclear as to what it actually
returns.

Expression::getUses isn't marked deprecated because the derived AST
classes still need to call 'getUses' because they can't call
'getRegisterUses' because it needs the definitions of those classes.
RegisterAST::getUses isn't marked deprecated because it gets explicitly
called by MultiRegisterAST::getUses.



To unsubscribe from these emails, change your notification settings at https://github.com/dyninst/dyninst/settings/notifications