🚀 go-pugleaf

Thanks, Remy for that explanation.   Hmm!  Not so obvious, as could be 
expected, of course.

Have just bought BDS2006 upgd for BCB6, (�ouch! - personal purchase).  Is 
there a way of having this and BCB6 installed on the same PC?   Could I 
install BCB on one drive and BDS on another, so keeping the Borland 
directories apart?  (I want to continue to service my BCB6 - NM internet 
products _and_ start to get to grips with Indy in BDS.)

Sorry, yet another and possibly daft, question but  can I have _both_ Indy9 
and Indy10 on the same PC using BDS?  (Different drives again?)  I would 
like to follow up your hint about looking at the Indy10 components(that 
interest me) - comparing them with those in Indy 9 to find out how things 
work.  (I haven't used Indy at all yet!)

Best regards,

Peter Evans.


"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:45085b6f@newsgroups.borland.com...
>
> "Peter Evans" <peter-evans@pelcaro.com> wrote in message
> news:45084d23@newsgroups.borland.com...
>
>> Have just got back into Borland's NGs.  This Indy 10 problem in BCB
>> (6Pro in my case) is still with us after more than a year.  I note from
> the
>> replies in this thread and those in the 21aug by Vlad that Remy is the
>> only person working in this area.  This prompts me to ask whether, or 
>> not,
>> any of us can help, and if so, how?
>
> Indy is open source.  Anyone can contribute to it.  The two biggest 
> problem
> areas are:
>
> 1) lack of suitable installation support for C++.  At one time, I was able
> to adapt the install scripts from Indy 9 to work with Indy 10.  But I 
> never
> got the chance to release them.  I have since moved on to making a ton of
> other (unrelated) architectural changes to Indy 10 to address other 
> issues,
> so I have yet to get back to a compilable state again.  I want to try
> compiling the current snapshot as-is, without all of my changes in place,
> but don't have much time to get around to it lately.
>
> 2) making sure all of the interfaces work in C++.  For example, I just
> recently had to change the interface design for the TIdHash classes 
> slightly
> because they were using Delphi features that don't work in C++.
> Specifically, they were returning arrays as their return values, which is
> something the C++ compiler will not allow, so the Delphi compiler produces
> the wrong function signatures when generating the C++ header files for the
> classes.
>
>
> Gambit
>
>