After thinking about it a bit, I can say that I wouldn't consider it. Let me explain my reasoning:
While in a declaration like this it might be rather clear:
var
a, b, c, d, e, f, g, h, i, j, k : Integer = 255;
The initialization will become rather lost if you have longer variable names and spread them across multiple lines (this coding style is used in the compiler for example):
var
SomeVariableName1,
SomeVariableName2,
SomeVariableName3,
SomeVariableName4,
SomeVariableName5,
SomeVariableName6,
SomeVariableName7,
SomeVariableName8,
SomeVariableName9,
SomeVariableName10: Integer = 255;
When looking at such code you might not notice that
SomeVariableName1 is initialized to some value.
I grant you that this might not make a difference when a new variable is added, cause if you don't realize that it's already initialized you'll just initialize it yourself (and the compiler could optimize away the initialization from the
var section).
When refactoring however or changing the type of a single variable this might however be significant (we've all had days where we thought we should have noticed that pesky
= 255 at the end (and we might even have), but for some reason we forgot it (e.g. someone distracted you or whatever) and then we had a lengthy debugging season on our hands).