SymbolsDidLoad is currently only implemented for ObjCLanguageRuntime,
but that doesn't mean that it couldn't be useful for other Langauges. Although
this change seems like it's generalizing for the sake of purity, this removes
Target's dependency on ObjCLanguageRuntime.
Details
Diff Detail
- Repository
- rL LLVM
Event Timeline
source/Target/Target.cpp | ||
---|---|---|
1670–1672 ↗ | (On Diff #202620) | Same question about runtime iteration as in the other review. |
Seems like we need a Process::SymbolsDidLoad(...) function that we can call. It should iterate over all loaded language runtimes (only loaded ones) and forward the list.
source/Target/Target.cpp | ||
---|---|---|
1670 ↗ | (On Diff #202620) | Seems like we should add a Process::SymbolsDidLoad() method that matches this method's signature and just call that. Process would iterate across all loaded language runtimes and call SymbolsDidLoad on any? |
source/Target/Target.cpp | ||
---|---|---|
1670 ↗ | (On Diff #202620) | Instead of adding Process::SymbolsDidLoad, I could instead iterate here over the loaded language runtimes with Process::GetLanguageRuntimes and call LanguageRuntime::SymbolsDidLoad on each one. What do you think? This would prevent us from having 3 classes with the method SymbolsDidLoad with the same signature. |
1670–1672 ↗ | (On Diff #202620) | Right, we should definitely iterate over loaded language runtimes instead of just using the ObjC runtime. Will update. |
source/Target/Target.cpp | ||
---|---|---|
1670 ↗ | (On Diff #202620) | That is fine as long as we iterate over all loaded language runtimes I am good. |