Hi John,
> I like proposal 2) below. It keeps things simple.
I came to the same conclusion. The only complication is that in
a multi-threaded environment the string value pointer could be
invalidated by another thread at any time. In a non-preemptively
scheduled threading system the workaround is to copy the string,
but what about a preemptively scheduled threading system? In
such a system a thread switch could happen between getting the
string attribute and copying it. Are preemptively scheduled
threading systems (e.g., pthreads) outside the scope of SCE-MI?
> > 2) The implementation returns a pointer to the string value [...]
> > The implementation guarantees the pointer is valid until
> > Shutdown() is called for read-only attributes. For
> > non-read-only attributes, the implementation guarantees the
> > pointer is valid until Shutdown() or
> > OverrideAttributeStringValue() of the attribute.
I meant to add the phrases `whichever comes first' at the end of
this paragraph.
Per
-- Per Bojsen Email: <bojsen@zaiqtech.com> Zaiq Technologies, Inc. WWW: http://www.zaiqtech.com 78 Dragon Ct. Tel: 781 721 8229 Woburn, MA 01801 Fax: 781 932 7488Received on Wed Mar 24 19:27:25 2004
This archive was generated by hypermail 2.1.8 : Wed Mar 24 2004 - 19:27:27 PST