Hello Hans,
Tuesday, April 8, 2008, 12:17:38 PM, you wrote:
deriving which I think is not used elsewhere. It will break a lot
of code, but it is easy to change, and also easy to make a
compatibility mode.
it's also easy to replace all the books, update all code repositories
and reteach all
On 8 Apr 2008, at 10:47, Bulat Ziganshin wrote:
deriving which I think is not used elsewhere. It will break a lot
of code, but it is easy to change, and also easy to make a
compatibility mode.
it's also easy to replace all the books, update all code repositories
and reteach all the programmers
Hello Hans,
Tuesday, April 8, 2008, 12:17:38 PM, you wrote:
deriving which I think is not used elsewhere. It will break a lot
of code, but it is easy to change, and also easy to make a
compatibility mode.
it's also easy to replace all the books, update all code repositories
and reteach
On 8 Apr 2008, at 15:26, PR Stanley wrote:
I'm sure you could introduce change gradually without too much pain.
So then you only have to get the compilers to gradually understand
it :-).
I personally think deriving is a descriptive term, now that I
understand its role better.
There are
