Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 334606

Summary:

[c++0x] Double right angle brackets formatting breaks list initializers when mixed inside a namespace

Product:

[Tools] CDT

Reporter:

David E. Narvaez <david.narvaez>

Component:

cdt-editor

Assignee:

Project Inbox <cdt-editor-inbox>

Status:

CLOSED DUPLICATE

QA Contact:

Anton Leherbauer <aleherb+eclipse>

Severity:

normal

Priority:

CC:

cdtdoug

Version:

7.0.1

Target Milestone:

---

Hardware:

OS:

Linux

Whiteboard:

Attachments:

Description	Flags
Example file for testing	none

Description David E. Narvaez

2011-01-17 22:19:52 EST

Build Identifier: M20100909-0800

I guess this is a hard one to catch:

Say you have your Code Style configured to have list initializers in the same line. Then, let's say you have a list initializer and you have double right angle brackets in the same file and these are both in a namespace.

Reproducible: Always

Steps to Reproduce:
1. Configure the Code Style to have list initializers in the same line of declaration
2. Open a namespace
3. Use double right angle brackets inside the namespace
4. Use list initializers in the same namespace
5. Try autoformatting

Comment 1 David E. Narvaez

2011-01-17 22:24:12 EST

Created attachment 186965 [details]
Example file for testing

An example file showing the situation. You can play around with formatting in this file. Notice that commenting the bogus function shows yet another formatting weirdness that may be related to the same issue.

Comment 2 Anton Leherbauer

2011-01-18 09:27:05 EST

This appears to be fixed with bug 333816.  Please confirm.

Comment 3 David E. Narvaez

2011-01-19 23:55:01 EST

(In reply to comment #2)
> This appears to be fixed with bug 333816.  Please confirm.

Confirmed, sorry for that: I lost track of the versions among my Eclipse installations.

Thanks again!

David E. Narváez

Comment 4 Anton Leherbauer

2011-01-20 02:36:40 EST

Thanks for verifying.

*** This bug has been marked as a duplicate of bug 333816 ***