While you're online: now that you've split the io ops into their
own separate file, their documentation isn't going to core_ops.pod
any more. The enclosed patch fixes this by autogenerating io_ops.pod
in the same fashion that core_ops.pod is generated, but I'm not sure
whether this is the right thing to do - do we want every ops lib to have
separate documentation, or should we just keep all of the documentation
in one place, in a single file?
Simon
--- Makefile.old Mon Jan 21 12:34:36 2002
+++ Makefile Mon Jan 21 12:35:05 2002
@@ -1,7 +1,7 @@
PERL = perl
RM_F = rm -f
-all: packfile-c.pod packfile-perl.pod core_ops.pod
+all: packfile-c.pod packfile-perl.pod core_ops.pod io_ops.pod
packfile-c.pod: ../packfile.c
perldoc -u ../packfile.c > packfile-c.pod
@@ -11,6 +11,9 @@
core_ops.pod: ../core.ops
perldoc -u ../core.ops > core_ops.pod
+
+io_ops.pod: ../io.ops
+ perldoc -u ../io.ops > io_ops.pod
clean:
$(RM_F) packfile-c.pod packfile-perl.pod
