You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IMHO the current parsing logic is a bit too strict when handling the space between host and code:
It requires exactly one SPACE
It requires SPACE and not a more general whitespace which includes TAB as well.
I suggest we relax these two requirements.
A secondary but somewhat related concern the parsing logic in some places uses ASCII whitespace and in some place uses SPACE. I think it would be much easier to have a single concept of white space that we use in the whole parsing algorithm.
This could be either:
ASCII whitespace: which includes U+0009 TAB, U+000A LF, U+000C FF, U+000D CR, or U+0020 SPACE. One concern is that it includes LF and CR which are not relevant given that parsing is happening on a single line.
Custom define white space for this spec to just be: U+0020 SPACE + U+0009 TAB
The text was updated successfully, but these errors were encountered:
IMHO the current parsing logic is a bit too strict when handling the space between host and code:
I suggest we relax these two requirements.
A secondary but somewhat related concern the parsing logic in some places uses ASCII whitespace and in some place uses SPACE. I think it would be much easier to have a single concept of white space that we use in the whole parsing algorithm.
This could be either:
U+0009 TAB, U+000A LF, U+000C FF, U+000D CR, or U+0020 SPACE
. One concern is that it includes LF and CR which are not relevant given that parsing is happening on a single line.The text was updated successfully, but these errors were encountered: