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

Indentation issues with doxygen comments #271

Closed
veripoolbot opened this issue Jul 21, 2010 · 2 comments
Closed

Indentation issues with doxygen comments #271

veripoolbot opened this issue Jul 21, 2010 · 2 comments

Comments

@veripoolbot
Copy link
Collaborator


Author Name: Scott Roland
Original Redmine Issue: 271 from https://www.veripool.org
Original Date: 2010-07-21


Here is a collection of indentation issues I see with Revision 629

// This is an example file to show the indentation errors I see with
// the verilog-mode.

// The assumption is that this file will be included into another
// file defining a module.

initial begin
    int unsigned count = 0;
    int value; // ERROR #1: value should align with count
    string source_str;
end

    task begin_trans // ERROR #2 task should align with end
      (input int h_stream ///<[in ] Handle of the stream to use
       );
    endtask : begin_trans

    //////////////////////////////////////////////////////////////////////
        // ERROR #3 Doxygen inline comment should not cause this indent

@veripoolbot
Copy link
Collaborator Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2010-07-21T10:42:41Z


Thanks for the report.

Mac, BTW I was going to argue the task is indented properly and it's the initial that is improper, but now that tasks and functions can now be global in SV I guess it makes sense they can be at column zero.

Also, one hackaround is this:

`ifdef NEVER
module just_for_emacs;
`endif
    initial ...

@veripoolbot
Copy link
Collaborator Author


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2014-11-06T21:37:09Z


Closing due to the age of the issue; please reopen if you still want this, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant