Delphi twain vcl code#

The VCL is an excellent tool for implementing the 'V' part of the 'Model-View-Controller' pattern, and should be left alone.ДЄll that is needed is a new, separate library to do the concern separating. The solution to this, it seems to me, needn't be painful. Its leanings are more towards consolidation of concerns into one honking big woe. The VCL doesn't really 'do' separation of concerns. You will recall the design principle called 'separation of concerns', which says it is a good idea to minimise dependencies between different functions of your program.

Delphi twain vcl code#

Remember: we already got some Pascal garbage collection in Delphi.NET - and that didn't work out brilliantly, did it? Also, if we get GC in native New Delphi, will it not introduce hideous data sharing problems with Olde Delf modules, like managed and unmanaged code in Visual C++? When you do garbage collection, you are handing off a piece of control that by rights belongs to the obsessed, micro-optimising programmer. This is what differentiates it from C# and Java, which emphasise portability and safety, but run in vast, cosy-but-stifling, virtual machines that arrive (in one case) as gargantuan downloads and (in the other) seem to need updating every 10 minutes. But I don't think it is right for native Delphi.Дelphi Object Pascal is surely supposed to be a 'as close to the metal as is sensible without being rust' sort of language.

Garbage collection is in general a great liberating thing. So with all this talk about smart pointers, I guess you are agin garbage collection? OK, I admit it.