Hi,
I took the action to check if the spec needs some language to clarify
that reusing SceMiMessageData objects and resending them is OK. The
current spec neither forbids nor explicitly allows this usage. This
means it is likely that different implementations will do different
things and it would seem useful to add clarifying language.
Send()
In Section 5.4.6.1, document p. 53, PDF p. 61, after the sentence
under `data' add:
This object may be arbitrarily modified after Send() and used in
an arbitrary number of Send() invocations to the same as well as
other message ports as long as these all have the same width.
Receive()
In Section 5.4.7.1, document p. 55, PDF p. 63, after the last paragraph
in the section add:
The class SceMiMessageData object passed to the receive callback may
be sent any number of times to any number of input ports as long as
the width of each of these ports is the same as the width of the
output port causing the receive callback. Modifying the
class SceMiMessageData object by casting away const leads to
undefined behavior.
Thanks,
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 Thu Nov 4 13:25:06 2004
This archive was generated by hypermail 2.1.8 : Thu Nov 04 2004 - 13:25:12 PST