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

documentation issue /*verilator public*/ #27

Closed
veripoolbot opened this issue Jul 30, 2008 · 1 comment
Closed

documentation issue /*verilator public*/ #27

veripoolbot opened this issue Jul 30, 2008 · 1 comment
Assignees
Labels
area: documentation Issue involves documentation resolution: fixed Closed; fixed

Comments

@veripoolbot
Copy link
Contributor


Author Name: Holger Wächtler
Original Redmine Issue: 27 from https://www.veripool.org
Original Date: 2008-07-30
Original Assignee: Wilson Snyder (@wsnyder)


Hi,
is the explanation of the documentation (website) correctly describing the access of private module signals?
shouldn't "top->v.signal" read "top->v->signal"?

@veripoolbot
Copy link
Contributor Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2008-07-30T20:07:31Z


Fixed for next release, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: documentation Issue involves documentation resolution: fixed Closed; fixed
Projects
None yet
Development

No branches or pull requests

2 participants