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

Additions to the internals documentation #483

Closed
veripoolbot opened this issue Apr 15, 2012 · 2 comments
Closed

Additions to the internals documentation #483

veripoolbot opened this issue Apr 15, 2012 · 2 comments

Comments

@veripoolbot
Copy link

@veripoolbot veripoolbot commented Apr 15, 2012


Author Name: Jeremy Bennett (@jeremybennett)
Original Redmine Issue: 483 from https://www.veripool.org
Original Date: 2012-04-15
Original Assignee: Jeremy Bennett (@jeremybennett)


I've added some more detail to the internals document. This is based on my recent coding experiences with Verilator, so emphasises the things that initially confused me.

I've also modified the Makefile so all the POD files (not just the main manual) are also generated as PDF.

@veripoolbot

This comment has been minimized.

Copy link
Author

@veripoolbot veripoolbot commented Apr 15, 2012


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2012-04-15T19:10:51Z


In git towards 3.833.

BTW you can just "git ci" each of your change sets, then use "git format-patch" to make the patch output. There's a huge number of web tutorials if you're interested.

@veripoolbot

This comment has been minimized.

Copy link
Author

@veripoolbot veripoolbot commented Apr 15, 2012


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2012-04-15T19:14:56Z


P.S. made some minor updates, the only major item is that one generally should use the methods defined in each AstXXYYZZ rather than op1p(), for example ifsp() (if-statements-pointers) instead of op1p().

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.