Alain,
I have both compilers, it's just that I primarily use Proton, as a personal preference. The information on both forums is helpful. Remember, at the very beginning, I said both are good products and you won't go wrong. BUT--that's ONLY because of contributors like DT. Without his contributions, I could not have made that statement. And that alone makes Proton a better compiler, because he may change jobs or focus some day, but both compilers will still remain. The fact is that Proton has a far better track record for actual improvements, while PBP has remained rather static. What, two new (significant) features added over the last five years? And one of those--Long's--was on Proton from the beginning!
I don't get it why people take personal offense when someone says product "a" is better than product "b". It's a lot like the lame pc software reviews of the 90's where the magazines would let readers vote, and make their conclusion based on the vote. Have you EVER seen someone vote saying "I made the wrong choice"?
Well, I did, and I'm man enough to admit it. That's why I have both. Do YOU have both? I once tried to give my PBP license away to a developer who's used Proton, and he wouldn't take it!
Sure, you can use DT's plug-ins. But if you are shopping for a new package, why bother? You can have the features built-in, with instructions on how to use them in the manual with Proton. All in one compiler without changing settings or including a hack. And at a lower price. And tighter asm output.
And, yes, Proton has its hacks available, too. But typically the popular hacks get implemented into new releases. Tim Box was the original developer of the Instant Interrupt concept for PBP. He also implemented it for Proton. So this is the perfect example, because now it's an integrated feature of Proton.
CNC guy--don't take me wrong, you have a good compiler, with good support. But I own both, and think Proton is better.
Bookmarks