\documentclass[nocolor,memo]{j3}
\renewcommand{\hdate}{6 January 2004}
\renewcommand{\vers}{J3/04-176}
\usepackage{lineno}
\usepackage{longtable}
\usepackage{xr}
\externaldocument{007}
\input pdftest
\begin{document}
\vspace{-10pt}
\begin{tabbing}
Subject: \hspace*{0.25in}\=Provide a specification that there are no
implicitly EXTERNAL procedures\\
From: \>Van Snyder\\
Reference: \>03-258r1, section 2.4.1\\
\end{tabbing}
\pagewiselinenumbers
\leftlinenumbers
\linenumbers*
\section*{Number}
TBD
\section*{Title}
\section*{Submitted By}
J3
\section*{Status}
For consideration.
\section*{Basic Functionality}
Provide a specification that there are no implicitly EXTERNAL procedures.
\section*{Rationale}
If one wishes to construct a program entirely from module procedures, it
would be useful if the processor could be instructed to announce an error
if there is a reference to a procedure that is not a module procedure, not
an intrinsic procedure, and has not explicitly been given the external
attribute.
\section*{Estimated Impact}
Minor. A simple statement described in Section 12, or maybe something on
the IMPLICIT statement.
\section*{Detailed Specification}
Add a specification that there are no implicitly EXTERNAL procedures.
One way to do this is to add a specification to the IMPLICIT statement,
say NOEXTERNAL, to indicate that no procedure is to be given the EXTERNAL
attribute implicitly. I understand that some processors have an
extension to allow an UNDEFINED specification to the IMPLICIT statement,
to indicate both the effect of the NONE specification, and the NOEXTERNAL
specification advocated here.
\section*{History}
\label{lastpage}
\end{document}