[info-performer] Re: Deallocating_Performer_memory

New Message Reply Date view Thread view Subject view Author view

From: John Kelso (kelso++at++vt.edu)
Date: 01/25/2003 07:50:03


Hi,

We do our best to get around the pfExit bug by having all of our Performer
code go out of scope.

Something like:

void performer(void) {
  all Performer code is here, or called from here
}

main () {
  performer()
  pfExit
}

We do a lot of other kludgey stuff to get around various Performer
weirdness. You might want to take a look at our generic DIVERSE dpf
"hello world" program. You can ignore the DIVERSE code and still see the
Performer work-arounds. I haven't messed with the work-arounds in
Performer 3.0 yet- it would be nice to see that they're no longer needed.
Or, maybe they've been replaced by new weirdnesses requiring different
work-arounds. I don't even want to think about what'll be needed to be
done for Windows...

http://www.diverse.vt.edu/dpf/releases/dpf-2.1.0/examples/helloWorld/hello.C

-John

----------------------------------------------------------------------
John Kelso email: kelso++at++vt.edu
Senior Research Associate phone: 540-231-2054
Computer Science Dept. fax: 540-231-2056
Virginia Tech
3030B Torgersen Hall, MS 0106 The DIVERSE Project:
Blacksburg, VA 24061 www.diverse.vt.edu


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Sat Jan 25 2003 - 07:52:22 PST

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