>It would be nice to have intelliJ keep the foo() inside the block.
Very good idea!
Hitting <Enter> at the |
if (condition) {|
foo();
could lead to:
if (condition) {
|
foo();
}
Regards,
Mike
>
>Subject: [Eap-list] Suggestions for improving auto { }
> From: "Edwin Delsman" <[EMAIL PROTECTED]>
> Date: Thu, 14 Mar 2002 10:32:53 +0100
> To: <[EMAIL PROTECTED]>
>
>I'm trying out IntelliJ and I've become very enthousiastic about it's merits
>in a very short time. However, there are some small inconveniences with
>auto-blocks when editing the following existing code (though you won't hear
>me arguing to turn the feature off!):
>
> if (condition)
> foo();
>
>If I want to add some extra statements in the if clause, I open a block
>behind the if. IntelliJ than produces this (effectively removing the foo()
>>from the controlled statement!):
>
> if (condition) {
> |
> }
> foo(); // foo placed outside the block: not as intended
>
>It would be nice to have intelliJ keep the foo() inside the block. The same
>applies to other places, such as after an else clause. A similar thing
>happens when editing:
>
> if (condition) {
> foo1();
> foo2();
> }
>
>When I need to add a statement before foo1() I'm accustomed to position the
>caret atfer the if () { and press Enter there. However, I then get a similar
>problem:
>
> if (condition) {
> |
> }
> foo1(); // code placed outside the block: not as intended
> foo2();
> } // unmatched closing brace
>
>It would be nice if IntelliJ could detect that the block is already closed
>and omits inserting the closing brace.
>
>Greetings,
>Edwin Delsman
>
>
>_______________________________________________
>Eap-list mailing list
>[EMAIL PROTECTED]
>http://www.intellij.com/mailman/listinfo/eap-list
_______________________________________________
Eap-list mailing list
[EMAIL PROTECTED]
http://www.intellij.com/mailman/listinfo/eap-list
