On Fri, 02 Dec 2011 17:24:11 -0000, Adam <a...@anizi.com> wrote:
Ok, fine, let me put it THIS way.
Suppose I use a parent library, and *I* don't update it.
The USER of my library provides an updated version for some
unrelated reason.
So.. the user has:
Parent.dll
Your.dll
Their.exe
and everything is working ok. Then they update Parent.dll to a new
version. And because D does not require 'abstract' on classes, it all
breaks?
But.. Your.dll has not been recompiled.. so how is D supposed to detect
this?
Or, were you suggesting the user supply a new Parent.dll to you, and you
rebuild Your.dll with it? In which case, when you run your unit tests you
will get an error, right?
Regan
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
