Markdown wiki backup
Revision | 3afd0c71c92664217ae2d5357ad005aeee3cc8fb (tree) |
---|---|
Zeit | 2016-10-30 02:34:19 |
Autor | OCTAGRAM <bo_ <gen@octa...> |
Commiter | OCTAGRAM <bo_ |
SOM 2.1 memory management
@@ -0,0 +1,10 @@ | ||
1 | +http://octagram.name/pub/somobjects/3.0beta/pdf/som/sdclient.pdf | |
2 | + | |
3 | +In contrast, the default policy in DSOM 2.x was a combination of caller-owned for in and inout parameters, dual-owned for out parameters and return results, and suppress_inout_free for inout parameters. | |
4 | + | |
5 | +To the caller, dual-owned looks no different than the default behavior. On the server side, dual-owned looks like object-owned; DSOM allocates and initializes the parameters, but frees nothing after method completion, except certain introduced pointers. | |
6 | + | |
7 | +in => caller-owned | |
8 | +inout => caller-owned, suppress_inout_free | |
9 | +out => dual-owned (object_owns on local and server) | |
10 | +result => dual-owned (object_owns on local and server) |