Eli Bendersky
2013-Jan-02 17:25 UTC
[LLVMdev] Renaming MCInstFragment to MCRelaxableFragment
Hello and happy 2013, Would anyone object to renaming MCInstFragment to MCRelaxableFragment? I believe the latter expresses this class's purpose much more clearly and avoids the confusion with MCDataFragments which also contains instructions. Eli
Rafael Espíndola
2013-Jan-03 19:31 UTC
[LLVMdev] Renaming MCInstFragment to MCRelaxableFragment
I guess that is OK, but wouldn't it be better to also rename MCDataFragments then? On 2 January 2013 12:25, Eli Bendersky <eliben at google.com> wrote:> Hello and happy 2013, > > Would anyone object to renaming MCInstFragment to MCRelaxableFragment? > I believe the latter expresses this class's purpose much more clearly > and avoids the confusion with MCDataFragments which also contains > instructions. > > Eli > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
Eli Bendersky
2013-Jan-03 19:38 UTC
[LLVMdev] Renaming MCInstFragment to MCRelaxableFragment
On Thu, Jan 3, 2013 at 11:31 AM, Rafael Espíndola <rafael.espindola at gmail.com> wrote:> I guess that is OK, but wouldn't it be better to also rename > MCDataFragments then? >I don't know what a more suitable name would be. Any ideas? Eli
Seemingly Similar Threads
- [LLVMdev] Renaming MCInstFragment to MCRelaxableFragment
- [LLVMdev] Renaming MCInstFragment to MCRelaxableFragment
- [LLVMdev] Renaming MCInstFragment to MCRelaxableFragment
- [LLVMdev] Proposal for -filetype=obj full big endian support
- [LLVMdev] Proposal for -filetype=obj full big endian support