Leaderboard

That is outrageous. Especially for older versions which were sold as a perpetual license. Now it seems that customers cannot legitimately continue to use software they own and have paid for. Is Delphi ransomware now?

The component vendor is applying a development methodology known as "wishful thinking". FastMM4 doesn't get this wrong.

As an aside to this. What happens if Emba goes bust? are we all just locked out of the software? I have an active subscription but I'm of the opinion that this change makes using Delphi a very risky choice as Emba seem prepared to cut us off from using the software we own. Why can't we just move an activation from one machine to another without needing to go through the process of phoning in to ask permission?

See this answer from Embarcadero to a customer who wants to increase the registration count: Reinstalling Windows without re-registering Delphi Update : The linked message was deleted by a moderator. Only visitors with enough reputation can view the original message.

If this is true, then Embarcadero is not anymore a Partner you can trust.

Well if you are working with ignoramuses you have to get the bigger guns out and install some commit hooks to prevent them from committing unresolved conflicts. Google will help you finding out how that works.

I like the MS VS way better than the EMBT BDS way.

Contacted Yaroslav and he confirms beta should be this summer/autumn.

I'd like to mention Parallels as a very good VM host as well.

Problem with TComponent (and subsequently its descendants) is that it implements interfaces but has reference counting disabled in _AddRef and _Release methods so it can be used like regular class. However, people often forget that in such cases _AddRef and _Release calls even though they don't do any counting will still be inserted by compiler and called for any interface reference to such object instance. So if there is alive interface reference to the object after calling Free that interface reference will contain dangling pointer and when such interface goes out of scope _Release will be called on already nuked object. While you may get away with such call without FastMM debugging mode, if it is turned on it will correctly identify the problem. Simple test case that will blow with FastMM in debug mode procedure TestComponent; var Comp: TComponent; Intf: IInterface; begin Comp := TComponent.Create(nil); Intf := Comp; Comp.Free; end;

There are no false positives to this - if FastMM reports this it's true. These errors are usually very subtle and the reference to that freed instance might only live a few cycles more and unless there does not happen another memory allocation that might reuse this particular piece of memory there will never be a defect (in terms of an AV happening or something) which is why this usually goes unnoticed by most until you enable this option which is not part of the build-in FastMM version (which is a shame!). It's unbelievable how ignorant some vendors can be...

See if my CodeRage 9 presentation gives you any useful ideas: http://w5a.com/u/coderage-9-talk

Whereas you feel safe with American companies which hand over everything on you to NSA and FBI as they do not risk to end up in jail. Come on, OrangeUI is probably an individual who sells his product. I am sure all of us have bought components from such individuals in the past. And, really, would you feel more comfortable if the site was in English and the download link was a direct file? or if the domain was orangeui.com?

I often wonder how many issues in a mature product are actually the misuse of Version Control..