This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 26362 - "Increase pointer by one. "
Summary: "Increase pointer by one. "
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: URL (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: Unsorted
Assignee: Anne
QA Contact: sideshowbarker+urlspec
URL:
Whiteboard:
Keywords:
Depends on: 25946
Blocks:
  Show dependency tree / graph
 
Reported: 2014-07-16 23:52 UTC by Albert Wiersch
Modified: 2015-06-17 15:49 UTC (History)
4 users (show)

See Also:

Attachments

Description Albert Wiersch 2014-07-16 23:52:10 UTC 
http://url.spec.whatwg.org/#host-parsing

[[
Increase pointer by one. 
]]

Should this be

If c is not the EOF code point then increase pointer by one.
Comment 1 Anne 2014-07-29 09:05:18 UTC 
The way the pointer thing in the specification works is that if you point beyond EOF it's still EOF. Is this actually a problem?
Comment 2 Albert Wiersch 2014-07-29 13:35:18 UTC 
It was an issue for me when programming in C/C++. I had to figured out the problem/bug. In my opinion, the text I suggested is less error prone and more precise.
Comment 3 Sam Ruby 2014-12-04 21:36:33 UTC 
This likely will become moot with the proposed parser rewrite.
Comment 4 Anne 2015-06-15 15:06:42 UTC 
Albert, were both instances of the step "Increase pointer by one." problematic in your implementation? It's not clear to which one you are referring here.
Comment 5 Albert Wiersch 2015-06-16 19:16:31 UTC 
Hi Anne,

The problematic step was the step after "If dots seen is 1 or 3, increase piece pointer by one." and the step before "If dots seen is 3 and c is not the EOF code point, parse error, return failure."