\documentclass[nocolor,memo]{j3} \renewcommand{\hdate}{31 August
2004} \renewcommand{\vers}{J3/04-379} \usepackage{lineno}
\usepackage{longtable} \usepackage{xr} \externaldocument{007}
\input pdftest \begin{document} \vspace{-10pt} \begin{tabbing}
Subject: \hspace*{0.25in}\=Allow empty CONTAINS part (hopefully
done)\\ From: \>Van Snyder\\ Reference: \>03-258r1, section 2.5,
04-189\\ \end{tabbing} \pagewiselinenumbers \leftlinenumbers
\linenumbers* \section{Number} TBD \section{Title} Allow empty
CONTAINS part. \section{Submitted By} J3 \section{Status} For
consideration. \section{Basic Functionality} Allow empty
CONTAINS part. \section{Rationale} Is there a good reason that a
module, procedure or type definition has to have procedure
definitions after the CONTAINS statement? What would be hurt by
allowing not to have any? Sometimes when programs are generated
automatically, they end up with an empty CONTAINS part, and then
you have to go fix it manually, or whine (ineffectually) to the
unsympathetic guys who