Marco Tech Blog

March 12, 2008

Handbook Note 112/113: Indy and Compatibility

Note 112 of 113 of Delphi 2007 Handbook

posted by marcocantu @ 1:41PM | 3 Comments [0 Pending]

Handbook Note 112/113 Indy and Compatibility 

The Indy project did a lot of breaking changes in the 
latest 10.x releases - virtual methods that became 
static, name changes, and many others. Targeting too 
many compilers does not help, either.

Being a library on which many other delphi libraries 
are based upon, those changes break a lot of things. 
In the past days I was trying to evaluate a library 
from Eldos, but it was impossible because most of the 
examples didn't work with Indy 10.2.3 I had to 
install to have some bugs fixed.

IMHO, or Codegear removes Indy from Delphi and add a 
library with better release management, or Codegear 
should "take control" of the Indy project and drive 
it through a proper management path.

Comment by Luigi D. Sandon on March 12, 15:24

Handbook Note 112/113 Indy and Compatibility 

I really hate that kind of unneeded changes. We are
still stuck on Indy 9 since it is too much work to
update to Indy 10... Codegear should take over the
library if you ask me and handle it as if it was some
normal VCL library of their own.

Comment by me on March 12, 17:12

Handbook Note 112/113 Indy and Compatibility 

 Totally agree. I had a problem with Indy not handling
very large streams, and posted a message on Indy news,
to be told that the problems I faced had been fixed
with the latest Indy. I updated (with difficulty) and
Yes, my problem had gone away. But my ongoing project
which used REMObjects were totally broken. My only
recourse was to un-install the later Indy and put the
one that came with BDS 2006 back on. This whole
episode cost me more than a weeks work, by the time I
had got the relevant replies from Indy etc. (The
support does still work. And thanks go to Remy, but
the whole experience was not good)

Comment by steve hughes on March 13, 11:22