InferiorCall is only ever used in Process, and it is not specific to
POSIX. By moving it to Process, we can remove all dependencies on plugins from
Process. Moving InferiorCall to Process seems to achieve this quite well.
Additionally, the name InferiorCall is a little vague now, so we rename
it something a bit more specific.
Details
Diff Detail
- Repository
- rL LLVM
Event Timeline
This seems like the right place to put it, it's clearly something you would do with a process.
I don't see any reason why this should be a private function. It's just a convenience wrapper around a bunch of other public functionality, and doesn't do anything that needs to be hidden from clients of Process. I wouldn't want somebody else to reinvent it if they needed to do the same thing.
However, InferiorCall is a pretty vague name for something that has a very specific task. Once it is part of Process, the "Inferior" bit is unnecessary, the Process IS the inferior... Maybe just CallVoidArgVoidPtrReturn? That's not too hideous.
I was going to say LGTM unless Jim has concerns, but looks like he cut me to the chase :-)
I don't think CallNoArgNoReturnFunc is the right name. This routine calls a function that takes no arguments but returns a void *.