Memory space in db loaders

Javier Abadia Miranda (abadia++at++sgonyx.ita.es)
Mon, 4 May 1998 12:48:02 +0000

• Next message: vee: "Memory space in db loaders"
• Previous message: Jonas Andersson: "Virtual cliptexture problems"
• Next in thread: Jay Gischer: "Memory space in db loaders"
• Reply: Jay Gischer: "Memory space in db loaders"

How is memory space managed in database loaders?

I have written a loader that is dinamically linked
and called with pfdLoadFile() mecanism.

During the app, several files are loaded by subsequent
calls to this pfdLoadFile().

My question is:

If I use static variables inside de loader's code, how many
copies of that variables exist ?

Do they get initialized each time the loader is called?

Otherwise, do they mantain the values from one call to
the next?

Which is the *politically correct* way of keeping
configuration modes, values and attributes from call
to call?

pfdSetConverterMode(someting);
pfdLoadFile(one file); /* with mode something */
pfdLoadFile(other file); /* with mode something also */

Thank you!

Aaadios

=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
            Submissions: info-performer++at++sgi.com
        Admin. requests: info-performer-request++at++sgi.com

• Next message: vee: "Memory space in db loaders"
• Previous message: Jonas Andersson: "Virtual cliptexture problems"
• Next in thread: Jay Gischer: "Memory space in db loaders"
• Reply: Jay Gischer: "Memory space in db loaders"

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:57:21 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.