>>>Lately I've been experimenting with a variation: RecordPositionSave() and RecordPositionRestore(). This follows a logical ( to me ) hierarchy of Object.Attribute.Action. But I'm finding the greatest benefit is this puts related methods next to each other when listed alphabetically, which makes them easier to find.
>>
>>Full ACK: I started with "ordered methods" when refactoring large methods, dividing them into smaller methods usually named
>>
>>LargeMethod
>>LargeMethod_EntryCheck
>>LargeMethod_DoOnething
>>LargeMethod_DoSomethingElse
>>
>>and so on. xxxGet and xxxSet were next from that ;-)
>
>That's exactly what prompted me to start doing this.
>
>>Java and C# translation can be machine-supported ;-)
>
>How so?

Ruleengine for renaming methods or creating wrappers