On 30/09/2016 17:24 μμ, Michalis Kamburelis wrote:
4. And how about going even more further, and just generate an
internal GUIDs (random, or based on a memory address) when no GUID is
explicitly specified? This way "is", "as", "Supports" always just
work. And it removes the need to do 1., 2., 3. above, of course.
Is there a drawback to doing this, that I don't see?
You assume that the interfaces are
1) user controlled
2) is not used outside from your own environment.
Both valid use cases but invalid assumptions. GUID needs to stay user
selectable otherwise you loose the ability to implement interfaces for
3rd party applications (banking, stock exchange, ms office etc).
Interfaces are compiler agnostic you might import them to use a 3rd
party library (eg. ADO) which has its own GUIDs that you must not change.
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
