Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

blog: fix yacc links #20434

Closed
bradfitz opened this issue May 19, 2017 · 7 comments
Closed

blog: fix yacc links #20434

bradfitz opened this issue May 19, 2017 · 7 comments
Labels
Documentation FrozenDueToAge help wanted NeedsFix The path to resolution is known, but the work has not been done.
Milestone

Comments

@bradfitz
Copy link
Contributor

As repoted by @Konstantin8105, https://blog.golang.org/generate has dead links to since-removed go tool yacc.

@bradfitz bradfitz added Documentation help wanted NeedsFix The path to resolution is known, but the work has not been done. labels May 19, 2017
@bradfitz bradfitz added this to the Unreleased milestone May 19, 2017
@odeke-em
Copy link
Member

Double drat, that article is gonna require a massive rewrite since it seemed to rely mostly on yacc for examples. Could this be something the DevExp group might be interested in? /cc @rakyll

@bradfitz
Copy link
Contributor Author

It doesn't need a rewrite. Just add a go get golang.org/x/tools/cmd/goyacc step. That makes the argument for "only developers run go generate, not users" even stronger, demonstrating that the developer might have tools available that the user doesn't.

@odeke-em
Copy link
Member

My bad, I hadn't realized that golang.org/x/tools/cmd/goyacc existed and that yacc hadn't been deleted to oblivion. Thanks for the explanation.

@pravj
Copy link
Contributor

pravj commented May 25, 2017

@bradfitz
I would like to fix this by pointing to the current location of yacc tool (goyacc).
Am I allowed to do it?

@bradfitz
Copy link
Contributor Author

@pravj, that'd be great. Thanks! See https://golang.org/doc/contribute.html

@gopherbot
Copy link

CL https://golang.org/cl/44230 mentions this issue.

@pravj
Copy link
Contributor

pravj commented May 25, 2017

@bradfitz
I have submitted a change list.
Do I need to add you as a reviewer from the UI?

@golang golang locked and limited conversation to collaborators May 25, 2018
gopherbot pushed a commit to golang/website that referenced this issue May 26, 2021
The post has a dead link to the Go version of Yacc (goyacc).
It was moved to 'golang.org/x/tools/cmd/goyacc' in CL 27325.

Fixes golang/go#20434.

Change-Id: I16e39d0bc2be422b129fd5cadd95f9b3a52c1abd
Reviewed-on: https://go-review.googlesource.com/44230
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
X-Blog-Commit: 83eaf8725de030de65c4ae73d82b1e8e002901a2
passionSeven added a commit to passionSeven/website that referenced this issue Oct 18, 2022
The post has a dead link to the Go version of Yacc (goyacc).
It was moved to 'golang.org/x/tools/cmd/goyacc' in CL 27325.

Fixes golang/go#20434.

Change-Id: I16e39d0bc2be422b129fd5cadd95f9b3a52c1abd
Reviewed-on: https://go-review.googlesource.com/44230
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
X-Blog-Commit: 83eaf8725de030de65c4ae73d82b1e8e002901a2
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Documentation FrozenDueToAge help wanted NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Development

No branches or pull requests

4 participants