[Lazarus] Collapsible try...finally...except...end blocks idea

[Martin Frb]

On 17/07/2018 10:34, el_es via Lazarus wrote:
> In short, to have the nested try...finally/except...end; blocks display
> in a single tier flatter manner, like
>
> try
>    try
>      code block 1;
>    finally
>      code block 2;
>    end;
> except
>    code block 3;
> end;
>
> display in Lazarus like
>
> try
>    code block 1;
> finally
>    code block 2;
> except
>    code block 3;
> end;
>
> with similar handling like the collapsible code blocks (e.g. a [+] or [-] on the gutter next to all the try's,
> depending on what the default setting is, to display or not to display nested try blocks)
> and handling of more 'sophisticated' nests like try...except...finally...except...end;
>
> (that means, in raw source code, this still will display like nested try blocks, not flat,
> and as such be fed into the compiler).
>
I dont think the code editor will change the indent, for that there are 
code formatters. (jedi)

Display a different indent from what is actually in the text brings up 
new issues, such as what happens if you edit spaces in the virtual 
indent. Where to they go in the real text?
Despite this, I am not convinced it is should be included. But if 
someone wants to do a package that install such a feature.....

Anyway the compiler already supports the indent you want (the compiler 
does not care about indent), so you can actually write it like this.

try try
   code block 1;
finally
   code block 2;
end;
except
   code block 3;
end;

All you have to deal with are:
- the double "try".
- the extra "end"
  
Several solutions

** 1)
Use fpc macro support (look up exact syntax, I am writing this from (distant) memory)
(this of course will trouble the editors folding detecting and outlining-markup)

{$macro on}
{$define try2:= try try}
{$define thenExcept := end; except}

try2
   code block 1;
finally
   code block 2;
thenExcept
   code block 3;
end;

The macro solution also makes it visually clear that you did not forget an opening try. After all it could be that there is an except block that covers a wider amount of code...

** 2)
Or (and that could be added to the editor):
Have a /hide option for {%region} (same as the current /fold). With /hide the region would be default disappear.

try
{%region /hide}try{%endregion}
   code block 1;
finally
   code block 2;
{%region /hide}end;{%endregion}
except
   code block 3;
end;