🚀 go-pugleaf

"Peter Evans" <peter-evans@pelcaro.com> wrote in message
news:4390a8b0$1@newsgroups.borland.com...

> I have downloaded Indy10.0.52 and find that the code and
> projects in Core, Protocols, etc., appear to be Delphi, when
> I thought I was going to get BCB!

The code has always been written in Pascal.  Most third-party components
are.

However, Indy 10 does not officially support BCB yet.  That is why there are
no BCB packages available.  C++ support is currently in the works.


Gambit

"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:4390ce48$1@newsgroups.borland.com...
>
>
> However, Indy 10 does not officially support BCB yet.  That is why 
> there are
> no BCB packages available.  C++ support is currently in the works.
>

Gambit,

Am I right in assuming that the C++ support will be tied to the new 
version of  Builder?

-- 
Bruce 

Thank you Remy(TeamB) for that reply, but I must be missing something 
somewhere.  For going back to the Indy website I find the following:
Indy.Sockets
Indy.Sockets is an open source socket library that supports clients, 
servers, TCP, UDP, raw sockets, as well as over 100 higher level protocols 
such as SMTP, POP3, NNTP, HTTP, and many more. Indy.Sockets is available for 
C#, C++, Delphi, Visual Basic.NET, any .NET language, and Kylix. 
Indy.Sockets FCL build is a managed assembly and is compatible with the 
Microsoft .NET framework, and Mono.

This says 'Indy.Sockets is available for ..., C++, ... '

On clicking on the link to Indy.Sockets in the above paragraph I get a page 
entitled What is Indy.Sockets?, containing a list 'Where To?' that gives a 
link Installation Instructions for Indy 10.  On following this link, I reach 
a page showing:

Indy10Install

All packages are followed by X0 (Where X is your Delphi verison).

  1.. Download source from the Development Snapshot.
Delphi / BCB Installation

  1.. Open and compile in the following order:
  2..
    1.. IndySystem (in Lib\System)
    2.. IndyCore (in Lib\Core)
    3.. IndyProtocols (in Lib\Protocols)
    4.. IndySuperCore (in Lib\SuperCore)
    If you are not using SuperCore, then you do not need to compile this 
package.
  3.. Now open and click install in the following order
  4..
  5..
    1.. dclIndyCore (in Lib\Core)
    2.. dclIndyProtocols (in Lib\Protocols)
    3.. dclSuperCore (in Lib\SuperCore)
    Only install this if you have compiled SuperCore.
This has a section Delphi / BCB Installation that briefly sets out what has 
to happen with the different downloaded .zip files.

It is at this point I find the code is purely Delphi, with no C++ in site. 
So is there no BCB code after all despite the titling of the paragraphs 
shown above.

I see that you mention that 'C++ support is currently in the works.', but 
how would I know that coming through what I have just shown.

I recall that on 23/11 you replied to my post saying:

'However, Indy 10 does not natively support BCB at this time, although there
are ways to install it into BCB 6 manually should you not mind a little
extra work on your part to get that far.'

I was expecting the extra work to show itself on following the thread I 
mentioned above.  Since I have missed it, where can I find it?  Or is it 
really that Indy is not out for BCB yet, and if so, what is a realistic date 
for its appearance from Indy?


Thank you in advance for further enlightenment.

Peter Evans.


"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:4390ce48$1@newsgroups.borland.com...
>
> "Peter Evans" <peter-evans@pelcaro.com> wrote in message
> news:4390a8b0$1@newsgroups.borland.com...
>
>> I have downloaded Indy10.0.52 and find that the code and
>> projects in Core, Protocols, etc., appear to be Delphi, when
>> I thought I was going to get BCB!
>
> The code has always been written in Pascal.  Most third-party components
> are.
>
> However, Indy 10 does not officially support BCB yet.  That is why there 
> are
> no BCB packages available.  C++ support is currently in the works.
>
>
> Gambit
>
> 

" Bruce Salzman" <bruce@nospam.org> wrote in message
news:4390f37c@newsgroups.borland.com...

> Am I right in assuming that the C++ support will be tied
> to the new version of  Builder?

It will support BCB 5 and 6 as well.


Gambit

"Peter Evans" <peter-evans@pelcaro.com> wrote in message
news:4390f596@newsgroups.borland.com...

> This says 'Indy.Sockets is available for ..., C++, ... '

"Indy.Sockets" is a general product name that encompasses both Indy 9 and
10.  Indy 9 has official support for C++.  Indy 10 does not (yet).  That
being said, Indy 10 can be installed and used in C++ as-is, if you don't
mind doing some manual work on your part to make it work.  Otherwise, wait
for the official support to be released.

> It is at this point I find the code is purely Delphi, with no C++ in site.

As I told you earlier, the source code has always been written in Pascal,
not C++.  BCB can use Delphi components because it ships with a Delphi
compiler as well as a C++ compiler.  Also, as I told you earlier, there are
no BCB installation files available for Indy 10 at this time.

> I was expecting the extra work to show itself on following the
> thread I mentioned above.

Go to http://www.deja.com and search through the newsgroup archives.  People
have posted instructions and links to email/websites for downloading
third-party packages to install Indy 10 in BCB 6.

> is it really that Indy is not out for BCB yet

It is not.

> if so, what is a realistic date for its appearance from Indy?

There is no definate ETA.  It may be later this month.  It may be next
month.  It may be 6 months from now.  It is whenever it is ready.


Gambit

Thank you Gambit(TeamB) for that extra advice - very useful particularly the 
deja URL, which I will follow up on.  ( I really don't mind doing the extra 
manual work you mentioned, so long as I know what it is I have to do.)

I did say that I was a complete novice with anything to do with Indy so your 
extra information is vital to me.  ( I now have 'Indy in Depth' to help.)

I also didn't know that there was a Delphi compiler in my BCB6 Pro - thanks 
for that, - it now makes sense to put Delphi sources into BCB directories. 
I was previously thinking that I would be having to find .obj or .dll files 
from somewhere.

Thanks also for clarifying the 'ETA' for the installation files for BCB 
installation files.  I won't hold my breath over it, and try to get on 
without it like everyone else.

Best regards,

Peter Evans.

PS.  I must have pressed a wrong button a few days as I returned a reply to 
'bruce@nospam.org' which is getting bounced.  Normal?



"Remy Lebeau (TeamB)"  wrote in message 
news:43949df5$1@newsgroups.borland.com...
>
> "Peter Evans"  wrote in message
> news:4390f596@newsgroups.borland.com...
>
>> This says 'Indy.Sockets is available for ..., C++, ... '
>
> "Indy.Sockets" is a general product name that encompasses both Indy 9 and
> 10.  Indy 9 has official support for C++.  Indy 10 does not (yet).  That
> being said, Indy 10 can be installed and used in C++ as-is, if you don't
> mind doing some manual work on your part to make it work.  Otherwise, wait
> for the official support to be released.
>
>> It is at this point I find the code is purely Delphi, with no C++ in 
>> site.
>
> As I told you earlier, the source code has always been written in Pascal,
> not C++.  BCB can use Delphi components because it ships with a Delphi
> compiler as well as a C++ compiler.  Also, as I told you earlier, there 
> are
> no BCB installation files available for Indy 10 at this time.
>
>> I was expecting the extra work to show itself on following the
>> thread I mentioned above.
>
> Go to http://www.deja.com and search through the newsgroup archives. 
> People
> have posted instructions and links to email/websites for downloading
> third-party packages to install Indy 10 in BCB 6.
>
>> is it really that Indy is not out for BCB yet
>
> It is not.
>
>> if so, what is a realistic date for its appearance from Indy?
>
> There is no definate ETA.  It may be later this month.  It may be next
> month.  It may be 6 months from now.  It is whenever it is ready.
>
>
> Gambit
>
>