Axel Dörfler wrote:
Better, but why change "must" to "should"? It's definitely a must.
I disagree, I don't like to tell programmers what to do and I feel that as a documentation writer it is my job to be humble and not assume too much. I wrote the following program to test whether or not it is possible to delete the message after assigning it to an Invoker via SetMessage(). #include <stdio.h> #include <Invoker.h> #include <Message.h> int main() { BInvoker* invoker = new BInvoker(); BMessage* message = new BMessage(); invoker->SetMessage(message); printf("The world is about to end\n"); delete message; printf("This message should not appear, the world has ended.\n"); delete invoker; printf("Now the world has definitely ended.\n"); return 0; } This program compiled and ran without issue on R1A4 and appears to be otherwise valid and correct, the world did not end, must is too presumptuous.