Add a list of mapping interface methods which are not supported by

rfc822.Message (per Barry's comments).

diff --git a/Doc/lib/librfc822.tex b/Doc/lib/librfc822.tex
index 56f6c7445769c0413a02619a716e98475c5d717c..87e16194b0b5509f311843ce240411f1d466338f 100644 (file)
--- a/Doc/lib/librfc822.tex
+++ b/Doc/lib/librfc822.tex
@@ -219,7 +219,10 @@ there is no matching header; and \code{len(\var{m})},
 \code{\var{m}.values()} and \code{\var{m}.items()} act as expected
 (and consistently).  \class{Message} instances also support the
 mapping writable interface \code{\var{m}[name] = value} and \code{del
-\var{m}[name]}.
+\var{m}[name]}.  \class{Message} objects do not support the
+\method{clear()}, \method{copy()}, \method{get()}, \method{popitem()},
+\method{setdefault()}, or \method{update()} methods of the mapping
+interface.
 
 Finally, \class{Message} instances have two public instance variables: