File tree 1 file changed +3
-3
lines changed
1 file changed +3
-3
lines changed Original file line number Diff line number Diff line change @@ -98,7 +98,7 @@ invoked to handle the operation, regardless.
98
98
-----------------------------
99
99
100
100
If all contexts were independent, it'd be hard to keep track of them,
101
- especially in error cases. That is solved this by creating a tree of
101
+ especially in error cases. That is solved by creating a tree of
102
102
"parent" and "child" contexts. When creating a memory context, the
103
103
new context can be specified to be a child of some existing context.
104
104
A context can have many children, but only one parent. In this way
@@ -383,8 +383,8 @@ precede the MemoryContext. This means the only overhead implied by
383
383
the memory context mechanism is a pointer to its context, so we're not
384
384
constraining context-type designers very much.
385
385
386
- Given this, routines like pfree their corresponding context with an
387
- operation like (although that is usually encapsulated in
386
+ Given this, routines like pfree determine their corresponding context
387
+ with an operation like (although that is usually encapsulated in
388
388
GetMemoryChunkContext())
389
389
390
390
MemoryContext context = *(MemoryContext*) (((char *) pointer) - sizeof(void *));
You can’t perform that action at this time.
0 commit comments