From 9e0cc156451770794e7eedbc0d9f45055aedd66f Mon Sep 17 00:00:00 2001
From: Sam Ruby <rubys@intertwingly.net>
Date: Sat, 29 Nov 2014 09:59:13 -0500
Subject: [PATCH] remove some definitions that are no longer necessary

---
 url.bs  | 17 -----------------
 url.src | 17 -----------------
 2 files changed, 34 deletions(-)

diff --git a/url.bs b/url.bs
index 2fe97c9..cebf78d 100644
--- a/url.bs
+++ b/url.bs
@@ -103,9 +103,6 @@ or in the range U+0061 to U+007A.
 
 <h3 id=parsers>Parsers</h3>
 
-<p>The <dfn>EOF code point</dfn> is a conceptual code point that signifies the end of a
-string or code point stream.
-
 Two types of parse errors are defined.  <dfn title='parse exception'>Parse
 exceptions</dfn> terminate parsing and must be implemented by all conforming
 implementations.  By contrast, user agents are encouraged, but not required,
@@ -113,20 +110,6 @@ to expose <dfn title='conformance error'>conformance errors</dfn> somehow.
 
 <p class=XXX>Add the ability to halt on the first conformance error.
 
-<p>Within a parser algorithm that uses a <var>pointer</var> variable, <dfn>c</dfn>
-references the code point the <var>pointer</var> variable points to.
-
-<p>Within a string-based parser algorithm that uses a <var>pointer</var> variable,
-<dfn>remaining</dfn> references the substring after <var>pointer</var> in the string
-being processed.
-
-<p class=example>If "<code>mailto:username@example</code>" is a string being
-processed and <var>pointer</var> points to "<code>@</code>",
-<a>c</a> is "<code>@</code>" and <a>remaining</a> is
-"<code>example</code>".
-
-
-
 <h2 id=percent-encoded-bytes>Percent-encoded bytes</h2>
 
 <p>A <dfn>percent-encoded byte</dfn> is "<code>%</code>", followed by
diff --git a/url.src b/url.src
index b856d06..b5aa950 100644
--- a/url.src
+++ b/url.src
@@ -116,9 +116,6 @@ or in the range U+0061 to U+007A.
 
 <h3 id=parsers>Parsers</h3>
 
-<p>The <dfn>EOF code point</dfn> is a conceptual code point that signifies the end of a
-string or code point stream.
-
 Two types of parse errors are defined.  <dfn title='parse exception'>Parse
 exceptions</dfn> terminate parsing and must be implemented by all conforming
 implementations.  By contrast, user agents are encouraged, but not required,
@@ -126,20 +123,6 @@ to expose <dfn title='conformance error'>conformance errors</dfn> somehow.
 
 <p class=XXX>Add the ability to halt on the first conformance error.
 
-<p>Within a parser algorithm that uses a <var>pointer</var> variable, <dfn>c</dfn>
-references the code point the <var>pointer</var> variable points to.
-
-<p>Within a string-based parser algorithm that uses a <var>pointer</var> variable,
-<dfn>remaining</dfn> references the substring after <var>pointer</var> in the string
-being processed.
-
-<p class=example>If "<code>mailto:username@example</code>" is a string being
-processed and <var>pointer</var> points to "<code>@</code>",
-<a>c</a> is "<code>@</code>" and <a>remaining</a> is
-"<code>example</code>".
-
-
-
 <h2 id=percent-encoded-bytes>Percent-encoded bytes</h2>
 
 <p>A <dfn>percent-encoded byte</dfn> is "<code>%</code>", followed by