comp.lang.idl-pvwave archive: archive » Re: Where is the trick in objects

Home » Public Forums » archive » Re: Where is the trick in objects

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: Where is the trick in objects [message #34623]

Thu, 10 April 2003 09:33

Pavel Romashkin
Messages: 166
Registered: April 1999

Senior Member

Thomas Gutzler wrote:
>
> P.S: I'm also looking for a better way to move the large arrays around.
> I think GetProperty, all=all isn't very fast, is it?

Don't move them around at all. To move them, you need at least twice the
memory than the array requires, and possibly three times as much if you
are not careful.
Use a pointer to put array onto the heap (if pushing RAM limits, fill
the already created pointer array with chunks of data). Then, don't use
assignment when you dereference it from the object, rather use in situ
dereferencing inside your function call (or method).
The advantage of heap is that the array can stay there forever, even if
you quit the process - you can give the pointer to it to another process
without ever reallocating memory. This way, I kept arrays as big as 1.2
Gb in RAM and switched from one GUI to another - there is no other way
to pass a variable this big as a parameter that I know of.

Cheers,
Pavel

Report message to a moderator

[Message index]

		Re: Where is the trick in objects By: Pavel Romashkin on Thu, 10 April 2003 09:33
		Re: Where is the trick in objects By: Thomas Gutzler on Thu, 10 April 2003 01:30
		Re: Where is the trick in objects By: David Fanning on Wed, 09 April 2003 21:22

Previous Topic:	Re: Proper pointer cleanup question
Next Topic:	Re: porting IDL code to OS X

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Oct 08 14:52:35 PDT 2025

Total time taken to generate the page: 0.00379 seconds