Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
www
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Fernando Ortiz
www
Commits
61924a99
Commit
61924a99
authored
Jun 13, 2003
by
Dan Egnor
Browse files
Options
Downloads
Patches
Plain Diff
Clarify allocation hooks
parent
e84f2c63
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
alloc.html
+2
-2
2 additions, 2 deletions
alloc.html
ref.html
+1
-1
1 addition, 1 deletion
ref.html
with
3 additions
and
3 deletions
alloc.html
+
2
−
2
View file @
61924a99
...
@@ -29,9 +29,9 @@ extern void (*oop_free)(void *ptr); /* <em>Free allocated memory.</em> */
...
@@ -29,9 +29,9 @@ extern void (*oop_free)(void *ptr); /* <em>Free allocated memory.</em> */
These are global function pointers, initialized by default to the standard C
These are global function pointers, initialized by default to the standard C
library functions
<em>
malloc
</em>
,
<em>
realloc
</em>
, and
<em>
free
</em>
.
library functions
<em>
malloc
</em>
,
<em>
realloc
</em>
, and
<em>
free
</em>
.
Applications using liboop may reset these pointers to allocation and
Applications using liboop may reset these pointers to allocation and
deallocation routines with a compatible interface;
component
s should use
deallocation routines with a compatible interface;
librarie
s should use
these function pointers wherever possible to allocate and release memory.
these function pointers wherever possible to allocate and release memory.
These pointers are normally set before calling any liboop co
mponents
; if they
These pointers are normally set before calling any liboop co
de
; if they
are changed during operation, the new
<em>
oop_free
</em>
and
are changed during operation, the new
<em>
oop_free
</em>
and
<em>
oop_realloc
</em>
functions should be
<em>
oop_realloc
</em>
functions should be
capable of handling memory obtained with the old
<em>
oop_malloc
</em>
.
capable of handling memory obtained with the old
<em>
oop_malloc
</em>
.
...
...
This diff is collapsed.
Click to expand it.
ref.html
+
1
−
1
View file @
61924a99
...
@@ -11,7 +11,7 @@
...
@@ -11,7 +11,7 @@
<pre>
<pre>
#include
<
oop.h
>
#include
<
oop.h
>
/*
<em>
For recommended use by oop components
.
</em>
*/
/*
<em>
Applications can set these; liboop libraries will use them
.
</em>
*/
extern void *(*
<a
href=
"alloc"
>
oop_malloc
</a>
)(size_t); /*
<em>
returns NULL on failure
</em>
*/
extern void *(*
<a
href=
"alloc"
>
oop_malloc
</a>
)(size_t); /*
<em>
returns NULL on failure
</em>
*/
extern void *(*
<a
href=
"alloc"
>
oop_realloc
</a>
)(void *,size_t); /*
<em>
returns NULL on failure
</em>
*/
extern void *(*
<a
href=
"alloc"
>
oop_realloc
</a>
)(void *,size_t); /*
<em>
returns NULL on failure
</em>
*/
extern void (*
<a
href=
"alloc"
>
oop_free
</a>
)(void *);
extern void (*
<a
href=
"alloc"
>
oop_free
</a>
)(void *);
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment