Madshi Avis 2

This is more like a gift than anything else really. I have been around in regard to programming with Delphi for decades and if one thing is important then it is exception handling. This requires all your attention, in case you think of handling it yourself. You definitely could use something that takes care of that and people probably underestimate all that is involved and how deep you need to dig into the stuff to make any sense of it. Not only any program you code but also the coding environment can simply throw ugly exceptions at you, leaving you with some vague address and description. IDE exceptions often persist and will require a reinstall. The time it would take to get rid of an access violation is long enough to reinstall Delphi twice or even more. I have been using this product for decades as well. (every time I produced buggy code preventing me from producing anything). This product is easy to use and for those who want more, there is more, more than you can imagine. Without debate it definitely ranks in the top 3 in regard to this line of sport and in my opinion it's the first. Recommended. I tried all exception handlers that are available currently but they were no match to this product. I can only recommend this. (after spending god knows how many hours trying to solve some problem myself) It takes away that worry that concern, I want to code and play around with Delphi, not hack into its interface to get rid of some access violation. Its way too boring too tedious and too complex, no fun in that so I was happy to find a remedy for it. Now Im not that bothered anymore when I get exceptions thrown at me by my program or the IDE. I can simply continue even without reinstalling Delphi completely. It has been around for decades as well, this can only mean one thing: it is reliable and it works like a charm!

The easiest and most reliable way to get rid of the daunting and oh so complicated task of exception handling. I have been using this component for over twenty years and at times when I was a little too optimistic thinking I could write an exception handler my own it took me nearly weeks to conclude I ran into a cul-de-sac. Fortunately madshis exception handler was still available and I never saw any exception escape his component. And bear with me in my enthousiasm I often wrote such awfully coded programs that caused exceptions before even seeing the main form lol. I tried all other available handlers but nearly needed a course to implement them. A must have for every serious programmer who doesnt want to saddle their clients up with a lot of questions and frustration as a consequence of poor exception handling. Ah well looking at the age of the component suite and its state, up and running, actually says more than enough. If I hadnt been so stubborn it would have saved me a siginificant part of all the time I spent coding. I wont go into details though lol. Thumbs up for this developer and his componentsuite!