Re: syntax completion - a bad thing?

[smize@news.imagin.net (Samuel Mize)]

In article <32FF06AE.190F@rational.com>, Greg Bek  <gab2@rational.com> wrote:
>Andrew Kelly wrote:
>> 
>>...
>> 
>> This seems, to me, to be more dangerous than it is useful ...
>> eg. If you accidentally delete the "end" from a nested "if",
>> where does the analyser stuff the "end"?  Indeed, even if it
>> gets the placement correct (eg. by inference from the text
>> indentation) if code statements have been inadvertantly deleted
>> as well, a clearly erroneous file will compile cleanly.
>>
>The syntax completion algorthim attempts to put closing constructs
>close the offending opening construct.  This tends to make the
>additions obvious to the user performing the editing.

If it happens while you are editing in that location, or if it
alters the indentation level someplace obvious.


>Similarly
>you can force it to break constructs with a well placed semi-colon
>when editing.
>
>Certainly there is a risk in the syntax complete creating
>eroneous code.  But programming is an intellectual activity,
>you don't do it with the brain turned off.

Well, he did say he wants it while editing (doing the intellectual
activity).  He just doesn't want it done behind his back when he's
not looking.  I can assure you that syntax completion is not AT ALL
obvious tothe user when it happens silently on closing the file, or
in a part of the file you don't happen to look at in that editing
session.


>I wouldn't trade my Apex Ada editor for any other option,...

Yes, it is a nice editor.  It would simply be nicer if the syntax
completion only happened under explicit user control.  As I recall
from some months ago, you could turn it off to keep it from
working behind your back, but then you couldn't invoke it manually.

Samuel Mize