[project @ akuchling-20030404043615-1825725f0edaa6ca]

[project @ 2003-04-03 20:36:06 by akuchling]
Rename can* and has* to can_* and has_*

1 files changed, 5 insertions, 5 deletions

diff --git a/Doc/pycrypt.tex b/Doc/pycrypt.tex
index 4276539..658112c 100644
--- a/Doc/pycrypt.tex
+++ b/Doc/pycrypt.tex
@@ -702,16 +702,16 @@ Returns true if the algorithm is capable of blinding data;
 returns false otherwise.  
 \end{methoddesc}
 
-\begin{methoddesc}{canencrypt}{}
+\begin{methoddesc}{can_encrypt}{}
 Returns true if the algorithm is capable of encrypting and decrypting
 data; returns false otherwise.  To test if a given key object can sign
-data, use \code{key.canencrypt() and key.hasprivate()}.
+data, use \code{key.can_encrypt() and key.has_private()}.
 \end{methoddesc}
 
-\begin{methoddesc}{cansign}{}
+\begin{methoddesc}{can_sign}{}
 Returns true if the algorithm is capable of signing data; returns false
 otherwise.  To test if a given key object can sign data, use
-\code{key.cansign() and key.hasprivate()}.
+\code{key.can_sign() and key.has_private()}.
 \end{methoddesc}
 
 \begin{methoddesc}{decrypt}{tuple}
@@ -732,7 +732,7 @@ big-endian integer must be relatively prime to \code{self.p-1}; an
 exception is raised if it is not.
 \end{methoddesc}
 
-\begin{methoddesc}{hasprivate}{}
+\begin{methoddesc}{has_private}{}
 Returns true if the key object contains the private key data, which
 will allow decrypting data and generating signatures.
 Otherwise this returns false.