🚀 go-pugleaf

[ followup set to microsoft.public.office.developer.vba ]

Martin E. Muehlmann wrote:

> loop 20000 times:
>     1. VBA app writes textfile w/ data. (sequential mode)
>     2. C program reads it and processes data
>     3. C program writes output textfile
>     4. VBA app read output file (sequential and binary mode)
> next
> 
> The problem is that I call this C program tousends of times and after
> each iteration I have less free resources.

If you are really sure that the C program is not causing the leaks, then 
you'll have to post your VBA code (that does the above) before anyone here 
can offer suggestions. It could be as simple as you not closing the shelled 
instances (which might be open in hidden mode), or it could be a lang. bug 
(doubt it).

As for the redesign, it really depends on what you are trying to do.  
Depending on the data size & type, and if you are the author of the C app, 
you could try switching to calling stdcall convention functions from VBA 
(which probably would be the fastest way).  You could also use memory mapped 
files and passing the pointers back and forth. As you can see, chances of 
you causing leaks increase as you step away from the VBA layer. I would 
definitely reconsider the file IO data exchange method though, FWIW.

  -- Dev