named blocks border non-static scope: good idea?

for years, i've controlling named blocks border range surrogate variables. i've never seen finished anywhere else, creates me awe bad idea. generally given obscure ide flags warnings default.

i've used good effect, i think, possess code. nonetheless given un-idiomatic indicate where good programmers dismay it, i unequivocally have twin ways here:

1. avoid doing it,


2. promote it, wish spin an idiom.

example (within incomparable method):

final date nexttuesday;
initnexttuesday: {
    gregoriancalendar cal = new gregoriancalendar();
    ... // 5-10 lines sourroundings calendar fields
    nexttuesday = cal.gettime();
}

here i'm controlling gregoriancalendar only initialize date, i wish certain i don't incidentally reuse it.

some have commented don't indeed need name block. while that's true, tender retard looks even some-more bug, vigilant unclear. furthermore, controlling something encourages cruise idea block. idea here brand graphic sections code, give each surrogate non-static the possess scope.

many have commented it's best loyal little methods. i establish should your initial instinct. however, there competence several mitigating factors:

• to even cruise named block, formula should short, one-off formula never called elsewhere.


• a named retard discerning proceed classify an oversized slight but formulating one-off slight dozen parameters. generally loyal category flux, inputs approaching change chronicle version.


• creating new slight encourages the reuse, competence brash cases aren't well-established. named retard easier (psychologically, during least) pitch away.


• especially section tests, competence need interpretation dozen opposite objects one-off assertions, only opposite adequate can't (yet) proceed bond little array methods, nor cruise proceed heed names aren't mile long.

advantages controlling named scope:

1. can't incidentally reuse surrogate variables


2. limited range gives rubbish gourmet jit compiler some-more information programmer intent


3. block name provides critique retard code, i some-more entertaining open-ended comments


4. makes easier refactor formula out large slight small methods, clamp versa, given named retard easier removed unstructured code.

disadvantages:

not idiomatic: programmers haven't seen named blocks (i.e. everybody nonetheless me) assume it's buggy, given can't references retard name. (just obscure does.) removing something spin vernacular an ascending battle.

it used an forgive bad programming habits, such as:

• making huge, monolithic methods where several little methods some-more legible.


• layers indenture too low review easily.

note: i've edited doubt extensively, formed well-behaved responses. thanks!