From 58f7d004fddd2cccdb019be59b6cc7a8abe50510 Mon Sep 17 00:00:00 2001 From: Martin Mares Date: Wed, 7 Jun 2000 13:25:53 +0000 Subject: Fixes to the progdoc. --- lib/event.c | 4 +--- lib/resource.sgml | 2 +- lib/slab.c | 4 ++-- 3 files changed, 4 insertions(+), 6 deletions(-) (limited to 'lib') diff --git a/lib/event.c b/lib/event.c index 788aab4..9b5870d 100644 --- a/lib/event.c +++ b/lib/event.c @@ -13,12 +13,10 @@ * Since BIRD is single-threaded, it requires long lasting tasks to be split to smaller * parts, so that no module can monopolize the CPU. To split such a task, just create * an &event resource, point it to the function you want to have called and call ev_schedule() - * to ask the core to run the event when nothing more important will require attention. + * to ask the core to run the event when nothing more important requires attention. * * You can also define your own event lists (the &event_list structure), enqueue your * events in them and explicitly ask to run them. - * - * The actual implementation is system dependent. */ #include "nest/bird.h" diff --git a/lib/resource.sgml b/lib/resource.sgml index df02bbf..6b6dd7d 100644 --- a/lib/resource.sgml +++ b/lib/resource.sgml @@ -21,7 +21,7 @@ modules of BIRD, deallocates everything automatically when a module shuts down and it's is able to print out the list of resources and the corresponding modules they are allocated by. -

Each allocated resource (and from now we'll speak about allocated +

Each allocated resource (from now we'll speak about allocated resources only) is represented by a structure starting with a standard header (struct -- cgit v1.2.3