Skip to content

fix(Network.Gopher.Util.Gophermap): don't use read to parse port#63

Open
sternenseemann wants to merge 1 commit into
masterfrom
port-render-parser
Open

fix(Network.Gopher.Util.Gophermap): don't use read to parse port#63
sternenseemann wants to merge 1 commit into
masterfrom
port-render-parser

Conversation

@sternenseemann
Copy link
Copy Markdown
Owner

@sternenseemann sternenseemann commented May 27, 2025

The current parser essentially assumes that ports are well formed and would probably crash in read if a malformed port number is part of the gophermap.

The current parser essentially assumes that ports are well formed and
would probably crash in `read` if a malformed port number is part of the
gophermap.
sternenseemann added a commit that referenced this pull request May 28, 2025
This continues the approach of re-using the Read instance of integer. An
alternative would be to reimplement the (subset of) integer parsing we
need ourselves, e.g. #63.
sternenseemann added a commit that referenced this pull request May 28, 2025
This continues the approach of re-using the Read instance of integer. An
alternative would be to reimplement the (subset of) integer parsing we
need ourselves, e.g. #63.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant