[Lazarus] OOP basics - 2

[Juha Manninen]

> By cleanly separating implementation layers and defining responsibilities
> and requirements for each in e hierarchical manner.
> Yes, the above sounds like a bunch of meaningless buzzwords ;-)
> It is hard to describe such things with words, but if you are interested
> you can look at the code in attached patch
> (it is very big, but most of it is code movement, which you can easily see
> if you use git).

I use git but I don't know all the features. How to compare the changes which 
are moved to another file?

I was looking at your patch with a diff tool (Kompare) and it looks good.
Not many typecasts. :-)
IMO it should be accepted. What are those backwards-compatibility concerns?

Juha