🚀 go-pugleaf

"hamid" <hrz_mir@yahoo.com> wrote in message
news:440ad603$1@newsgroups.borland.com...

> Whenever I use the TIdHTTP component I face a compiler error mentioned in
> the 411th line of the file "IdWinsock2.hpp", (typedef TWSAProtocol_InfoW
> *LPWSAProtocol_InfoW;) with the following message: ", expected"
>
> How can I solve the problem?

Which specific version and build of Indy are you using?


Gambit

The version that has been integrated with BCB2006. I faced the error using BCB2006. I temporarily solved the problem by defining the required structs by copying the defintion can be found in Indy website. But I'm not sure that I have used the same struct defintion as integrated with BCB2006. So any runtime error can be predicted.

"Hamid" <hrz_mir@Yahoo.com> wrote in message
news:440c8f53$1@newsgroups.borland.com...

> The version that has been integrated with BCB2006.

Which says nothing helpful.  Please specify the EXACT version and build.
BDS 2006 ship with both Indy 9 and 10.  You did not say which one you are
using (probably Indy 9), and I do not know which builds were actualy
shipped.

In any case, you are probably using an old build anyway, because the current
snapshot build does not declare LPWSAProtocol_InfoW at all, thus there would
be no such compiler error.  And certainly not on line 411, considering that
IdWinSock2.hpp is only 300-odd lines long to begin with.


Gambit

This is the version of the BDS 2006 that I am using:
 

Borland® C++Builder® Preview for Microsoft® Windows™ Version 10.0.2151.25345 Copyright © 2005 Borland® Software Corporation. All Rights Reserved.


The version of the indy components, IndyCore100.bpl, IndyProtocols100.bpl, and IndySystem100 is 10.0.0.17.


As for lines number, I wonder what's wrong with my Idwinsock2.hpp because it includes more than 2200 lines.


Moreover, I added the lines below to temporarily solve the problem.


// hamid - start
#pragma pack(push,1)
struct TWSAProtocolChain
{

public:
	int ChainLen;
	int ChainEntries[7];
} ;
#pragma pack(pop)

#pragma pack(push,1)
struct TWSAProtocol_InfoA
{

public:
	int dwServiceFlags1;
	int dwServiceFlags2;
	int dwServiceFlags3;
	int dwServiceFlags4;
	int dwProviderFlags;
	#pragma pack(push,1)
	GUID ProviderId;
	#pragma pack(pop)
	int dwCatalogEntryId;
	#pragma pack(push,1)
	TWSAProtocolChain ProtocolChain;
	#pragma pack(pop)
	int iVersion;
	int iAddressFamily;
	int iMaxSockAddr;
	int iMinSockAddr;
	int iSocketType;
	int iProtocol;
	int iProtocolMaxOffset;
	int iNetworkByteOrder;
	int iSecurityScheme;
	int dwMessageSize;
	int dwProviderReserved;
	char szProtocol[256];
} ;
#pragma pack(pop)

#pragma pack(push,1)
struct TWSAProtocol_InfoW
{

public:
	int dwServiceFlags1;
	int dwServiceFlags2;
	int dwServiceFlags3;
	int dwServiceFlags4;
	int dwProviderFlags;
	#pragma pack(push,1)
	GUID ProviderId;
	#pragma pack(pop)
	int dwCatalogEntryId;
	#pragma pack(push,1)
	TWSAProtocolChain ProtocolChain;
	#pragma pack(pop)
	int iVersion;
	int iAddressFamily;
	int iMaxSockAddr;
	int iMinSockAddr;
	int iSocketType;
	int iProtocol;
	int iProtocolMaxOffset;
	int iNetworkByteOrder;
	int iSecurityScheme;
	int dwMessageSize;
	int dwProviderReserved;
	WideChar szProtocol[256];
} ;
#pragma pack(pop)

typedef TWSAProtocol_InfoA *PWSAProtocol_InfoA;
typedef TWSAProtocol_InfoW *PWSAProtocol_InfoW;
struct _TRANSMIT_FILE_BUFFERS;
typedef _TRANSMIT_FILE_BUFFERS *PTransmitFileBuffers;
// hamid - end

"hamid" <hrz_mir@yahoo.com> wrote in message
news:440d6719$1@newsgroups.borland.com...

> The version of the indy components, IndyCore100.bpl,
> IndyProtocols100.bpl, and IndySystem100 is 10.0.0.17.

That is a very old version.  The current snapshot version is 10.1.5.

> As for lines number, I wonder what's wrong with my Idwinsock2.hpp
> because it includes more than 2200 lines.

Like I said, you have a very old version of Indy 10.  In that version,
IdWinSock2.pas was not set up for C++ yet.  Please upgrade to the current
10.1.5 snapshot.


Gambit

Thank you very much for your help. Would you please let me know how I can find the latest version of Indy 1.0. I downloaded its latest vesrion (I hope) from its website but I wonder why they stopped supporting their components written in Builder. Only Delphi versions are avalable. Sorry for inconvenience, but that would be great if you could help me...

"Hamid" <hrz_mir@Yahoo.com> wrote in message
news:440e820f$1@newsgroups.borland.com...

> Thank you very much for your help. Would you please let me
> know how I can find the latest version of Indy 1.0.

Follow the links on Indy's website (http://www.indyproject.org) for the
development snapshot.

> I downloaded its latest vesrion (I hope)

What EXACTLY did you download?

> I wonder why they stopped supporting their components written in Builder.

They didn't.  Indy 10 is a major re-write over Indy 9.  It has taken time to
get the new source code to work under C++ again without all kinds of
compiler issues.  The C++ support is not finished just yet, but it is close.
I am working on it personally (in fact, I am about the only C++ member of
Indy who is working on it).


Gambit

I checked this website and found the components here : http://www.indyproject.org/Sockets/Download/Files/Indy10.en.iwp

But as they mentioned, the only available version is 10.0.52 which is old. Moreover, the prepared components have been designed in Delphi not BCB or BDS. Would you please let me know where I can find the version that you mentioned?

"hamid" <hrz_mir@yahoo.com> wrote in message
news:4412a9dc$1@newsgroups.borland.com...

> I checked this website and found the components here:
> http://www.indyproject.org/Sockets/Download/Files/Indy10.en.iwp
>
> But as they mentioned, the only available version is 10.0.52 which is old.

Please re-read that page again.  That same page has the download link for
the latest "Development Snapshot".

> Moreover, the prepared components have been designed in
> Delphi not BCB or BDS.

Most third-party components in general are written in Delphi Pascal, not
C++.  All version of BCB, and C++ for BDS, can use Delphi components.


Gambit

Hi Remy,

I am very interested in the Indy support for the C++ personality of 
BCB2006.  When Ininstalled BDS2006 I had an early version that did not 
warn about C++ compatibility of Indy 10 and I installed Indy 10.  Now I 
am trying to update (actually a bug fix) in one of my apps.  I am trying 
to move everything from BCB5 to BDS2006...

Anyhow, I only need the IdHTTP client.  I use this in my web update 
mechanism.  If at least this is stable in the latest version of Indy 10 I 
think I will be OK.

I need a quick fix.  I either need to get Indy 10 working, or downgrade 
BDS2006 to Indy 9.

Can you help, or at least point me to a procedure for downgrading to Indy 
9?

Any help would be greatly appreciated.

Thanks in advance,
Fred.


"Remy Lebeau \(TeamB\)" <no.spam@no.spam.com> wrote in
news:4415e32f$1@newsgroups.borland.com: 

> 
> "hamid" <hrz_mir@yahoo.com> wrote in message
> news:4412a9dc$1@newsgroups.borland.com...
> 
>> I checked this website and found the components here:
>> http://www.indyproject.org/Sockets/Download/Files/Indy10.en.iwp
>>
>> But as they mentioned, the only available version is 10.0.52 which is
>> old. 
> 
> Please re-read that page again.  That same page has the download link
> for the latest "Development Snapshot".
> 
>> Moreover, the prepared components have been designed in
>> Delphi not BCB or BDS.
> 
> Most third-party components in general are written in Delphi Pascal,
> not C++.  All version of BCB, and C++ for BDS, can use Delphi
> components. 
> 
> 
> Gambit
> 
> 
> 

"Fred Hebert" <fhebert@nospam.fjhconsulting.com> wrote in message
news:Xns97918B62FACFDfhebertfjhconsulting@207.105.83.66...

> I am very interested in the Indy support for the C++ personality of
> BCB2006.

A lot of people are.

> When Ininstalled BDS2006 I had an early version that did not
> warn about C++ compatibility of Indy 10 and I installed Indy 10.
> Now I am trying to update (actually a bug fix) in one of my apps.
> I am trying to move everything from BCB5 to BDS2006...

Indy 10 is not ready for C++ just yet.

> Anyhow, I only need the IdHTTP client.  I use this in my web update
> mechanism.  If at least this is stable in the latest version of Indy 10 I
> think I will be OK.

I cannot answer that at this time.  The Protocols package of Indy 10 (which
defines all of the higher-level components, such as TIdHTTP) is not finished
being C++-enabled yet.  I've only gotten the Core and System packages
finished yet (which the Protocols package builds on top of).

> I need a quick fix.

Sorry, I don't have one for you.

> Can you help, or at least point me to a procedure for downgrading
> to Indy 9?

I do not have those intructions.


Gambit