No one in particular. We use 20+ different component packages where I work. All are statically linked into the executables. A while ago we changed the build process to compile all applications using component source rather than the supplied dcus. The main impetus being we could move to newer versions of Delphi without waiting on the component vendors to catch up. I was amazed at the amount of third party code that had warnings that weren't addressed. Some were potential sources of memory leaks, access violations, Most were just sloppy programming.
Kenneth Cochran Just wondered. I have had similar experiences with multiple vendors. And some of the warnings are things which I think they were very unwise to (apparently) ignore.
No one in particular. We use 20+ different component packages where I work. All are statically linked into the executables. A while ago we changed the build process to compile all applications using component source rather than the supplied dcus. The main impetus being we could move to newer versions of Delphi without waiting on the component vendors to catch up. I was amazed at the amount of third party code that had warnings that weren't addressed. Some were potential sources of memory leaks, access violations, Most were just sloppy programming.
ReplyDeleteKenneth Cochran Just wondered. I have had similar experiences with multiple vendors. And some of the warnings are things which I think they were very unwise to (apparently) ignore.
ReplyDeleteBeen there, done that, fixed the vendor's crap code in a branch and merged in new versions.
ReplyDelete