Make sure exports treat dart: libs specially just like imports.

docs/language/dartLangSpec.tex

 \documentclass{article}
 \usepackage{epsfig}
 \usepackage{dart}
 \usepackage{bnf}
 \usepackage{hyperref}
 \newcommand{\code}[1]{{\sf #1}}
 \title{Dart Programming Language  Specification \\
 {\large Draft Version 0.61}}
 \author{The Dart Team}
 \begin{document}
@@ skipping 465 matching lines @@
 \ref{variables}: Type promotion support added.
 
 \ref{formalParameters}: refined scope rules.
 
 \ref{classes}: Banned name clashes between type variables and members etc.
 
 \ref{factories}: Banned default values in redirecting factories.
 
 \ref{constants}: Added constant conditional expressions.
 
-\ref{strings}: Allow adjacent single and multiine strings to concatenate. Allow escaped newlines in multiline strings.
+\ref{strings}: Allow adjacent single and multiline strings to concatenate. Allow escaped newlines in multiline strings.
 
 \ref{conditional}: Type promotion support added.
 
 \ref{logicalBooleanExpressions}: Type promotion support added.
 
 \ref{logicalBooleanExpressions} - \ref{bitwiseExpressions}, \ref{operatorPrecedence}: Increased precedence of bitwise operations to be higher than equality and relational expressions.
 
 \ref{identifierReference}: Clarified static type rules. Type promotion support added.
 
 \ref{typeTest}: Type promotion support added.
 
 \ref{if}: Type promotion support added.
 
 \ref{return}: Added warning if \RETURN{} without expression mixed with \RETURN{} with an expression.
 
+\ref{exports}: Ensure that exports treat \code{dart:} libs specially, like imports do.
+
 \ref{typePromotion}: Added notion of type promotion.
 
 \ref{typedef}: Banned all recursion in typedefs.
 
 
 \section{Notation}
 \label{notation}
 
 We distinguish between normative and non-normative text. Normative text defines the rules of Dart. It is given in this font. At this time, non-normative text includes:
 \begin{itemize}
@@ skipping 4771 matching lines @@
 
 Then, for each entry mapping key $k$ to declaration $d$ in $NS$,  $d$ is made available in the top level scope of $L$ under the name $k$ unless either:
 \begin{itemize}
 \item
 a top-level declaration with the name $k$ exists in $L$, OR
 \item a prefix clause of the form  \AS{} $k$ is used in $L$.
 \end{itemize}
 
 \rationale{The greatly increases the chance that a member can be added to a library without breaking its importers.}
 
-If a name $N$ is referenced by a library $L$ and $N$ would be introduced into the top level scope $L$ by an import from a library whose name begins with \code{dart:} and an import from a library whose name does not begin with \code{dart:}:
+If a name $N$ is referenced by a library $L$ and $N$ would be introduced into the top level scope of $L$ by an import from a library whose URI begins with \code{dart:} and an import from a library whose name does not begin with \code{dart:}:

[ahe, 2013/10/11 05:21:03]

This sentence contains another use of "name" that should be changed to URI.

[gbracha, 2013/10/11 19:13:42]

Done.

 \begin{itemize}
 \item The import from \code{dart:} is implicitly extended by a \code{\HIDE{} $N$} clause.
 \item A static warning is issued.
 \end{itemize}
 
 \rationale {
 Whereas normal conflicts are resolved at deployment time, the functionality of \code{dart:} libraries is injected into an application at run time, and may vary over time as browsers are upgraded.  Thus, conflicts with \code{dart:} libraries can arise at runtime, outside the developerÕs control. To avoid breaking deployed applications in this way, conflicts with the \code{dart:} libraries are treated specially.
 
 It is recommended that tools that deploy Dart code produce output in which all imports use show clauses to ensure that additions to the namespace of a library never impact deployed code.
 }
 
-If a name $N$ is referenced by a library $L$ and $N$ is  introduced into  the top level scope $L$ by more than one import, and not all the imports denote the same declaration, then:
+If a name $N$ is referenced by a library $L$ and $N$ is  introduced into  the top level scope of $L$ by more than one import, and not all the imports denote the same declaration, then:
 \begin{itemize}
 \item A static warning occurs.
 \item If $N$ is referenced as a function, getter or setter, a \code{NoSuchMethodError} is raised. 
 \item  If $N$ is referenced as a type, it is treated as a malformed type.
 
 \end{itemize}
 
 We say that the namespace $NS$ {\em has been imported into} $L$.
 
 \commentary{
@@ skipping 67 matching lines @@
 \begin{itemize}
 \item If $C_i$ is of the form \code{\SHOW{} $id_1, \ldots, id_k$} then let 
 
 $NS_i = \SHOW{}([id_1, \ldots, id_k], NS_{i-1}$).  
 \item If $C_i$ is of the form \code{\HIDE{} $id_1, \ldots, id_k$} 
 
 then let $NS_i = \HIDE{}([id_1, \ldots, id_k], NS_{i-1}$). 
 \end{itemize}
 
 For each
-entry mapping key $k$ to declaration $d$ in $NS_n$ an entry mapping $k$ to $d$ is added to the exported namespace of $L$ unless a  top-level declaration with the name $k$ exists in $L$.  We say that $L$ {\em re-exports library } $B$, and also that $L$ {\em re-exports namespace } $NS_n$. When no confusion can arise, we may simply state that $L$ {\em re-exports }$B$, or that $L$ {\em re-exports }$NS_n$.
+entry mapping key $k$ to declaration $d$ in $NS_n$ an entry mapping $k$ to $d$ is added to the exported namespace of $L$ unless a  top-level declaration with the name $k$ exists in $L$.  
+
+If a name $N$ is referenced by a library $L$ and $N$ would be introduced into the exported namespace of $L$ by an export from a library whose URI begins with \code{dart:} and an export from a library whose name does not begin with \code{dart:}:

[ahe, 2013/10/11 05:21:03]

Ditto.

[gbracha, 2013/10/11 19:13:42]

Done.

+\begin{itemize}
+\item The export from \code{dart:} is implicitly extended by a \code{\HIDE{} $N$} clause.
+\item A static warning is issued.
+\end{itemize}
+
+\rationale{
+See the discussion in section \ref{imports} for the reasoning behind this rule.
+}
+
+We say that $L$ {\em re-exports library } $B$, and also that $L$ {\em re-exports namespace } $NS_n$. When no confusion can arise, we may simply state that $L$ {\em re-exports }$B$, or that $L$ {\em re-exports }$NS_n$.
 
 It is a compile-time error if a name $N$ is re-exported by a library $L$ and $N$ is  introduced into the export namespace of $L$ by more than one export, unless each all exports refer to same declaration for the name $N$.  It is a static warning to export two different libraries with the same name.
 
 
 
 \subsection{Parts}
 \label{parts}
 
 A library may be divided into {\em parts}, each of which can be stored in a separate location. A library identifies its parts by listing them via \PART{} directives. 
 
@@ skipping 682 matching lines @@
 \item The names of compile time constant variables never use lower case letters. If they consist of multiple words, those words are separated by underscores. Examples: PI,  I\_AM\_A\_CONSTANT.
 \item The names of functions (including getters, setters, methods and local or library functions) and non-constant variables begin with a lowercase letter. If the name consists of multiple words, each  word (except the first) begins with an uppercase letter.  No other uppercase letters are used. Examples: camlCase, dart4TheWorld
 \item The names of types (including classes and type aliases) begin with an upper case letter.  If the name consists of multiple words, each  word  begins with an uppercase letter.  No other uppercase letters are used. Examples: CamlCase, Dart4TheWorld.
 \item The names of type variables are short (preferably single letter). Examples: T, S, K, V , E.
 \item The names of libraries or library prefixes never use upper case letters. If they consist of multiple words, those words are separated by underscores. Example: my\_favorite\_library.
 \end{itemize}
 }
 
 
 \end{document}