Devart Forums

I'm trying to use 7.0.1 with RadStudio/C++Builder 2010, and it's failing to compile "Scasn1.hpp".

These lines (55,56) cause the problem:
....
TLexemInfos FElems;
TLexemInfos FArray;

The (first) error is
[BCC32 Error] Scasn1.hpp(55): E2303 Type name expected

TLexemInfos doesn't seem to be defined in any of the HPP files....???

XS 10
SB 7.0.1

Also have this problem after upgrade from 6.6.9 to 7.0.1:
[bcc32 Error] ScASN1.hpp(56): E2303 Type name expected
[bcc32 Error] ScASN1.hpp(56): E2139 Declaration missing ;
[bcc32 Error] ScASN1.hpp(57): E2303 Type name expected
[bcc32 Error] ScASN1.hpp(57): E2238 Multiple declaration for 'TLexemInfo::TLexemInfos'
[bcc32 Error] ScASN1.hpp(56): E2344 Earlier declaration of 'TLexemInfo::TLexemInfos'
[bcc32 Error] ScASN1.hpp(57): E2139 Declaration missing ;
Failed

The issue is related to С++ Builder 10 compiler specificity. To solve the issue, comment out the following lines in the ScASN1.hpp file:

ViktorV wrote:The issue is related to С++ Builder 10 compiler specificity. To solve the issue, comment out the following lines in the ScASN1.hpp file:

Code: Select all

  TLexemInfos FElems;
  TLexemInfos FArray;

Did you mean "RadStudio 10" or "RadStudio 2010"? I have 2010, and I think zat is using 10...

I'll give that a try. I considered it, but thought it would make the following C++ members misaligned compared to the Delphi ones...

roddyp wrote: I'll give that a try. I considered it, but thought it would make the following C++ members misaligned compared to the Delphi ones...

Ah. They're the last elements in the structure.

Thanks very much. That works fine now, and - better yet - is successfully negotiating SSH MAC with a system we'd previously been unable to work with

ViktorV wrote:The issue is related to С++ Builder 10 compiler specificity. To solve the issue, comment out the following lines in the ScASN1.hpp file:

Code: Select all

  TLexemInfos FElems;
  TLexemInfos FArray;

Rad Studio Seattle (RS 10 ) now compiled without error.

It is good to see that the issue has been solved. Feel free to contact us if you have any further questions about SecureBridge.