Aaarrgghh, when did they add the rest of the to the help. It wasnt
there last time I read it probably in D2.
On 2 Sep 99 at 11:40, Aaron Scott-Boddendijk wrote:
> >> It's not the problem of NOT including the Borland shared Memory
> >> Manager if strings are being used?
> >> in the DLL uses statements??
>
> > No, thats only required for sharing long strings. Hmm. maybe it is.
> > I will have another look at it later.
>
> As the snippet from the help below states... Strings ain't the only evil...
> All dynamic arrays as well or anything allocated with New or GetMem...
> so that's likely to cover a lot of the VCL...
>
> "If a DLL exports routines that pass long strings or dynamic arrays
> as parameters or function results (whether directly or nested in records
> or objects), then the DLL and its client applications (or DLLs) must all
> use the ShareMem unit. The same is true if one application or DLL
> allocates memory with New or GetMem which is deallocated by a call
> to Dispose or FreeMem in another module. ShareMem should always
> be the first unit listed in any program or library uses clause where it
> occurs."
>
> --
> Aaron Scott-Boddendijk
> Jump Productions
> (07) 838-3371 Voice
> (07) 838-3372 Fax
>
>
> ---------------------------------------------------------------------------
> New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
>
Rohit
======================================================================
CFL - Computer Fanatics Ltd. 21 Barry's Point Road, AKL, New Zealand
PH (649) 489-2280
FX (649) 489-2290
email [EMAIL PROTECTED] or [EMAIL PROTECTED]
======================================================================
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
