search for: createrelocationread

...amp;ri, ArrayRef<uint8_t> content); 2. Override one or both these methods in the <target name>ELFFile class. B: ===== 1. Create new class `ELFRelocationReader` and factor out `ELFReference` creation into the methods of this class. 2. Add new virtual function `createRelocationReader` to the `ELFFile` to create an instance of the `ELFRelocationReader`. 3. Subclass `ELFRelocationReader` and implement a target specific relocation reading. 4. Override `ELFFile::createRelocationReader` to create `ELFRelocationReader` subclass. In both implementations we just move some portion of...

Hi, Thanks for the explanation. If I understand you properly you suggest to move relocation parsing to the class with the following interface. Right? Who will be user of this class? If it is still only ELFFile class, what benefits will we get from separation of this logic? template <class ELFT> class ELFRelocationReader { public: ELFRelocationReader(.....); // Returns all created