Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
L
liboop
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Magnus Holmgren
liboop
Commits
f54a4518
Commit
f54a4518
authored
24 years ago
by
Dan Egnor
Browse files
Options
Downloads
Patches
Plain Diff
iconv const
parent
1663582c
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
oop-www.h
+2
-2
2 additions, 2 deletions
oop-www.h
with
2 additions
and
2 deletions
oop-www.h
+
2
−
2
View file @
f54a4518
...
@@ -19,10 +19,10 @@ void oop_www_register(oop_source *);
...
@@ -19,10 +19,10 @@ void oop_www_register(oop_source *);
/* Release any resources associated with the event manager, and
/* Release any resources associated with the event manager, and
unregister it with libwww. This will leave libwww with no event manager. */
unregister it with libwww. This will leave libwww with no event manager. */
void
oop_www_cancel
();
void
oop_www_cancel
(
void
);
/* Use libwww's memory management for liboop.
/* Use libwww's memory management for liboop.
** If you use this, you must do so before any other liboop function! ** */
** If you use this, you must do so before any other liboop function! ** */
void
oop_www_memory
();
void
oop_www_memory
(
void
);
#endif
#endif
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