Re: [cdt-dev] Refactorings you are missing

[Doug Schaefer <dschaefer@xxxxxxx>]

Very cool. I can't wait to see what you can come up with!

Thanks!

Diug

Sent from my BlackBerry 10 smartphone on the Rogers network.

From: Sergey Prigogin

Sent: Saturday, May 11, 2013 10:51 AM

To: CDT General developers list.

Reply To: CDT General developers list.

Subject: Re: [cdt-dev] Refactorings you are missing

On Sat, May 11, 2013 at 5:20 AM, Simon Taddiken <simon.taddiken@xxxxxxxxxxxxxx> wrote:

Thank you very much for your suggestions. I will most definitely not be able to implement all of your ideas within the scope of my bachelor thesis but I will try to identify some most wanted refactorings to make my work a useful contribution to the CDT project.

Am I right that the current C-Refactoring framework is only internal API and should thus not be accessed by plugins? So the preferred way for me to introduce a new refactoring which uses this framework is to "simply" put its sources into org.eclipse.cdt.internal.ui.refactoring.xyz and then submit a patch later on if I want it to be integrated into an official release?

Yes. 

greetings,
Simon

-sergey 

On 10.05.2013 22:49, Jan Baeyens wrote:

These are things that work in java and I really miss in CDT.
So I support this list.

On 10-May-13 21:12, Nathan Ridge wrote:

As a full-time Eclipse CDT user, I have many suggestions on this front.

In addition to the refactorings that were already mentioned, I think
it would be nice to see the following:

  - "Create method" as a quick fix when a method is unresolved
  - "Create function" as a quick fix when a function is unresolved
  - "Create class/struct" as a quick fix when a type is unresolved
  - "Inline variable" as the complement of "extract variable"
  - "Extract method" and "inline method" (analogous to "extract variable" and "inline variable")
  - Replace "auto" with the type it stands for
  - Replace a conventional for loop with a range-based for loop (need to detect where this is possible)

Also, here's a user interface improvement to the rename refactoring
that recent versions of ReSharper do for C#: rather than forcing
the user to invoke a rename refactoring, they detect when the user
changed an identifier via regular typing, and suggest to perform
the corresponding rename refactoring. I think it would be awesome
if CDT could do this.

Regards,
Nate
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev