[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 122650] New: inadequate c c++ indentation logic after scope entry ( curly brace )
From:       kdevelop-bugs-admin () barney ! cs ! uni-potsdam ! de
Date:       2006-02-24 15:31:54
Message-ID: 20060224163152.122650.erayo () bilkent ! edu ! tr
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=122650         
           Summary: inadequate c c++ indentation logic after scope entry (
                    curly brace )
           Product: kdevelop
           Version: 3.3.1
          Platform: unspecified
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: erayo bilkent edu tr


Version:           3.3.1 (using KDE 3.5.1, Mandriva Linux Cooker i586 - Cooker)
Compiler:          Target: i586-mandriva-linux-gnu
OS:                Linux (i686) release 2.6.12-12mdk

after legitimate line breaks, the indentation logic breaks.

        for (typename list<Node *>::iterator i = node->children.begin();
             i != node->children.end(); i++) {
               wohoo this sucks
          this does not suck
        }

here, the indentation calculates the line saying "wohoo this sucks" while it should \
indent on line saying "this doesn't suck" (I am using indentation length of 2)

it is indenting with respect to the line containing "i != node->..." this means that \
it is not finding the start of the statement. the last time i looked into this we \
were going backwards looking for a brace and start of the line. this definitely does \
not work for multi-line statements... neither does it really know about syntax. we do \
have a parser don't we?


[prev in list] [next in list] [prev in thread] [next in thread]