On 8-4-2022 11:26, Michael Van Canneyt wrote:
The duplications are within sets of units with similar names for
different component packages. It is only logical to also use that.
There is no need to force the unit as disambiguator.
I want to be able to use the unit as disambiguator.
That is clear. What isn't clear is why this is needed in a way that
forces changes (and incompatibilities) on users apps to solve IDE problems.
IOW in which cases is disambiguation in the class registration of the
generated app needed?
Sure, the IDE is also a FPC/Lazarus app, but it has more leeway for
solutions that doesn't require changes to the way EVERY APP streams its
forms.
That's the whole point of the exercise.
But given that we will offer the backwards compatibility flag, it is
not 'forcing'.
This is a nonsense argument to make discussion go away. Enough such
flags that an user only finds out when he is actually having problems is
enough to turn them away from Lazarus permanently.
--
_______________________________________________
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus
