From 68d66328363805550c9ba80676fb9ab1436adc3d Mon Sep 17 00:00:00 2001
From: Tim Edwards <tim@opencircuitdesign.com>
Date: Fri, 22 Sep 2023 16:31:36 -0400
Subject: [PATCH] Documented the "def write -anal" command option, which had
 previously been implemented without being documented.

---
 doc/html/def.html | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/doc/html/def.html b/doc/html/def.html
index f9d4f000..900d0f40 100644
--- a/doc/html/def.html
+++ b/doc/html/def.html
@@ -32,7 +32,7 @@ Read or write DEF format files.
 	   <DT> <B>read</B> <I>filename</I> [<B>-labels</B>] [<B>-annotate</B>]
 			[<B>-noblockage</B>]
 	   <DD> Read a DEF file <I>filename</I>[<B>.def</B>]
-	   <DT> <B>write</B> [<I>cell</I>] [<B>-units</B> <I>value</I>]
+	   <DT> <B>write</B> [<I>cell</I>] [<B>-units</B> <I>value</I>] [<B>-anal</B>]
 	   <DD> Write DEF for current or indicated cell named <I>cell</I>
 	   <DT> <B>help</B>
 	   <DD> Print help information (command summary)
@@ -84,6 +84,13 @@ Read or write DEF format files.
       the "lef" section of the magic technology file, or in a technology
       LEF file read prior to reading the DEF file). <P>
 
+      The "<B>-anal</B>" option for "<B>def write</B>" satisfies the
+      (very dubious) rule interpretation that "NONDEFAULT RULE" blocks
+      must contain a rule for every metal layer.  This is based on a
+      ridiculous interpretation of a specification that is poorly
+      worded and ambiguous.  The interpretation makes no sense
+      whatsoever.  But some tools will not accept the more rational
+      interpretation. <P>
    </BLOCKQUOTE>
 
 <H3>Implementation Notes:</H3>