Home > Software engineering >  In Vs2010 cstrings & problem
In Vs2010 cstrings & problem

Time:09-19

Problem, the code as shown in picture

CodePudding user response:

Cstrings are pre-allocated memory space, if space is insufficient, can reallocate memory space, since the size of the version is set, sVersion is in front of the incoming can specify the size?

CodePudding user response:

reference 1st floor light bamboo hat reply:
cstrings are pre-allocated memory space, if space is insufficient, can reallocate memory space, since the size of the version is set, sVersion is in front of the incoming can specify the size,
not specified, and the upper is not my decision,

CodePudding user response:

DLL interface parameters using cstrings class object?

CodePudding user response:

DLL export functions, if not the same compiler to use the basic data types, such as char *, WCHAR *, cstrings, string each compiler implementation is not the same! So their memory structure is different, the collapse is a matter of time before

CodePudding user response:

reference 4 floor hurryboylqs response:
DLL export functions, if not the same compiler to use the basic data types, such as char *, WCHAR *, cstrings, string each compiler implementation is not the same! So their memory structure is different, collapse is a matter of time before the
the all know, you said that the interface is not active, others will die

CodePudding user response:

SVersion=Versionch;

CodePudding user response:

refer to 6th floor schlafenhamster response:
sVersion=Versionch;
it is no good

CodePudding user response:

Cstrings (LPCSTR LPSZ);
Throw (CMemoryException);

What is "no"?

CodePudding user response:

VC6 DLL, if can't modify the DLL, then try to engineering use VC6 compile, generally of the same version of the compiler would be a good compatibility between
Or under VC6 redo a DLL to encapsulate the DLL

CodePudding user response:

references 9 f zgl7903 response:
VC6 DLLS, if you can't modify the DLL, can try using VC6 compile the project, by the same version of the compiler would be a good compatibility between
Or under VC6 redo a DLL to encapsulate the DLL
2010 must use the floor, that is to say must use VC6 generated, 2010 of the upper layer must be VC6 tuning the 2010, can't change, ha ha

CodePudding user response:

reference 4 floor hurryboylqs response:
DLL export functions, if not the same compiler to use the basic data types, such as char *, WCHAR *, cstrings, string each compiler implementation is not the same! So their memory structure is different, collapse is a matter of time before the
learning wrote before seemingly graph save trouble didn't pay attention to

CodePudding user response:

refer to 12 floor marslycan reply:
Quote: refer to 4th floor hurryboylqs response:

DLL export functions, if not the same compiler to use the basic data types, such as char *, WCHAR *, cstrings, string each compiler implementation is not the same! So their memory structure is different, collapse is a matter of time before the
learning wrote before seemingly graph save trouble didn't note

It is the premise of the same compiler, so if we want to write, so must be with the source code rather than just a DLL

CodePudding user response:

Refer to the below and see if there's any help to you:
http://www.cnblogs.com/cnmyp/archive/2011/04/03/2004177.html
  • Related