Dave Bartolomeo 4c23ad100e C++: Rename a few IR APIs ...

There are a few IR APIs that we've found to be confusingly named. This PR renames them to be more consistent within the IR and with the AST API:

`Instruction.getFunction` -> `Instruction.getEnclosingFunction`: This was especially confusing when you'd call `FunctionAddressInstruction.getFunction` to get the function whose address was taken, and wound up with the enclosing function instead.

`Instruction.getXXXOperand` -> `Instruction.getXXX`. Now that `Operand` is an exposed type, we want a way to get a specific `Operand` of an `Instruction`, but more often we want to get the definition instruction of that operand. Now, the pattern is that `getXXXOperand` returns the `Operand`, and `getXXX` is equivalent to `getXXXOperand().getDefinitionInstruction()`.

`Operand.getInstruction` -> `Operand.getUseInstruction`: More consistent with the existing `Operand.getDefinitionInstruction` predicate.

2019-02-06 22:43:49 -08:00

..

escape.cpp

C++: Force LF for .c,.cpp,.h,.hpp

2018-09-23 16:23:52 -07:00

escape.expected

C++: Fix a couple IR-related tests to handle new directory tree

2018-09-04 09:05:33 -07:00

escape.ql

C++: Rename a few IR APIs

2019-02-06 22:43:49 -08:00

points_to.expected

C++: Fix a couple IR-related tests to handle new directory tree

2018-09-04 09:05:33 -07:00

points_to.ql

C++: Fix a couple IR-related tests to handle new directory tree

2018-09-04 09:05:33 -07:00

ssa_escape.expected

C++: Fix a couple IR-related tests to handle new directory tree

2018-09-04 09:05:33 -07:00

ssa_escape.ql

C++: Rename a few IR APIs

2019-02-06 22:43:49 -08:00