forbid field name conflict in class hierarchy

[spir]

On Tue, 16 Nov 2010 05:37:52 -0500
bearophile <bearophileHUGS at lycos.com> wrote:

> spir:
> 
> > (and bug-prone, because sometimes the absence of a fields seems not caught, for any reason), so I add fields to the top type.
> 
> What do you mean? Do you have an example?
> (Adding fields to the top type doesn't look like a good idea, generally).
> 
> Bye,
> bearophile

PS: And I guess clients of the lib face the same issues.

denis
-- -- -- -- -- -- --
vit esse estrany ☣

spir.wikidot.com