🚀 go-pugleaf

"nicolasr" <nicolasrNOSPAMATSIGNgmx.net> wrote in message
news:40733f34@newsgroups.borland.com...

> 1) I would like to use the std::string class for parameters
> of the exported functions. Are there any issues I should
> be aware of with this?

That depends on what environments you want to use your DLL from exactly.  In
general, though, I would suggest avoiding using classes of any kind as the
function parameters.  They will usually not be very portable.  You can use
them inside the DLL as much as you want, though.

> The DLL will only be used from C++ code, most likely only from BCB.

Well, it makes a big difference whether it will be used ONLY by BCB, or just
MOSTLY by BCB.  As soon as you introduce more environments, you increase the
number of compatibility issues that you have to deal with.

> 3) Below is my DLL code. The client code loads the DLL
> dynamically and calls the Validate function. The Validate
> function accepts the name of an internal function to call
> and a std::string parameter specifying a file name that it
> passes on to the internal function.

I would suggest you use raw char* pointers whenever you use strings for
exported function parameters.  Those are the most compatible types of
strings across environments.

> After the line "ifstream in..." the "fileName" content is ???? like
> something corrupts the stack?

Very possibly.


Gambit