Re: 'Occurrence' OpenGOOP Object

[Jean-Pierre D. <jea...@tr...>]

Jim,

I think that by using CLNs within labview.exe to functions like AllocOccu=
r and DeallocOccur you can create (new at each call) and
destroy occurences. However, I don't know how platform (in)dependant it i=
s. I'm sure Rolf has more to say about this...

Jean-Pierre


----- Message d'origine -----=20
De : "Jim Kring" <ji...@ji...>
=C0 : "'OpenGToolkit-Developers'" <ope...@li...urcefo=
rge.net>
Envoy=E9 : 16 d=E9cembre, 2003 23:06
Objet : 'Occurrence' OpenGOOP Object


Hello All,

One thing that I have found bothersome about occurrences is that the
'Generate Occurrence' function is more of an Occurrence "constant" than a
"generator".  Each call to an instance of 'Generate Occurrence' will retu=
rn
the same occurrence.  So, I wrapped the occurrence primitives in a stripp=
ed
down OpenGOOP Class.  The data store contains only an occurrence, and the=
re
is one unique occurrence per object instance (since the data core is a
reentrant LV2 global, called by reference).  Another added benefit of hav=
ing
OpenGOOP wrapper VIs around the occurrence primitives is that they have
error IO, which makes data flow sequencing possible without the classic
one-frame sequence structure.

So, I have a few questions:

Does it make sense to augment the default behavior of occurrences?  If so=
,
what features and behaviors should be implemented?  Is this tool useful?

Regards,

-Jim