From c3c764644798cf20ab0c887620a90b1cb22fde1c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Henrik=20Grubbstr=C3=B6m=20=28Grubba=29?=
<grubba@grubba.org>
Date: Tue, 10 Feb 1998 20:15:17 +0100
Subject: [PATCH] Merged with the Pike 0.5 version 1.64 (1.62 - 1.64). 1.63:
Trig.pike.pmod => Trig.pmod. 1.64: Minor Gdbm changes.
Rev: tutorial/tutorial.wmml:1.67
---
tutorial/tutorial.wmml | 22 +++++++++++-----------
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/tutorial/tutorial.wmml b/tutorial/tutorial.wmml
index d62b1de2da..62d49dfff3 100644
--- a/tutorial/tutorial.wmml
+++ b/tutorial/tutorial.wmml
@@ -3309,7 +3309,7 @@ Here is an example of a simple module:
constant PI = 3.14159265358979323846264338327950288419716939937510;
float cos2(float f) { return pow(cos(f),2.0); }
</example>
-if we save this short file as <tt>Trig.pmod.pike</tt> we can now use this
+if we save this short file as <tt>Trig.pmod</tt> we can now use this
module like this:
<example language=pike>
int main()
@@ -6172,7 +6172,7 @@ might not be available in your Pike depending on whether the gdbm library
was available on your system when Pike was compiled.
<hr noshade size=1>
-<method name=Gdbm.create title="open database">
+<method name=Gdbm.gdbm->create title="open database">
<man_syntax>
int create();<br>
int create(string <I>file</I>);<br>
@@ -6204,7 +6204,7 @@ can be left in an unusable state if Pike is terminated abnormally.
<hr noshade size=1>
-<method name=Gdbm.close title="close database">
+<method name=Gdbm.gdbm->close title="close database">
<man_syntax>
void close();<br>
</man_syntax>
@@ -6215,9 +6215,9 @@ This closes the database.
<hr noshade size=1>
-<method name=Gdbm.store title="store a value in the database">
+<method name=Gdbm.gdbm->store title="store a value in the database">
<man_syntax>
-int Gdbm.store(string <I>key</I>, string <I>data</I>);<br>
+int store(string <I>key</I>, string <I>data</I>);<br>
</man_syntax>
<man_description>
Associate the contents of <i>data</i> with the key <i>key</i>. If the key <i>key</i>
@@ -6229,7 +6229,7 @@ the database was not open for writing.
<hr noshade size=1>
-<method name=Gdbm.fetch title="fetch a value from the database">
+<method name=Gdbm.gdbm->fetch title="fetch a value from the database">
<man_syntax>
string fetch(string <I>key</I>);<br>
</man_syntax>
@@ -6241,7 +6241,7 @@ If there was no such key in the database, zero is returned.
<hr noshade size=1>
-<method name=Gdbm.delete title="delete a value from the database">
+<method name=Gdbm.gdbm->delete title="delete a value from the database">
<man_syntax>
int delete(string <I>key</I>);<br>
</man_syntax>
@@ -6253,7 +6253,7 @@ if the key does not exist.
<hr noshade size=1>
-<method name=Gdbm.firstkey title="get first key in database">
+<method name=Gdbm.gdbm->firstkey title="get first key in database">
<man_syntax>
string firstkey();<br>
</man_syntax>
@@ -6265,7 +6265,7 @@ database.
<hr noshade size=1>
-<method name=Gdbm.nextkey title="get next key in database">
+<method name=Gdbm.gdbm->nextkey title="get next key in database">
<man_syntax>
string nextkey(string <I>key</I>);<br>
</man_syntax>
@@ -6283,7 +6283,7 @@ for(key=gdbm->firstkey(); k; k=gdbm->nextkey(k))<br>
<hr noshade size=1>
-<method name=Gdbm.reorganize title="reorganize database">
+<method name=Gdbm.gdbm->reorganize title="reorganize database">
<man_syntax>
int reorganize();<br>
</man_syntax>
@@ -6297,7 +6297,7 @@ can take a LOT of time to run.
<hr noshade size=1>
-<method name=Gdbm.sync title="synchronize database">
+<method name=Gdbm.gdbm->sync title="synchronize database">
<man_syntax>
void sync();<br>
</man_syntax>
--
GitLab