You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Author Name: Kaushal Modi
Original Redmine Issue: 1038 from https://www.veripool.org
Original Date: 2016-02-19
Hi,
I was leaning towards getting auto named ends functionality just like the auto endcomments functionality that we have right now.
Initially my thought was to add a defvar which would use ":" instead of "//" when auto inserting the named ends (instead of named comments).
That too would only happen for these endings (as per IEEE SystemVerilog Standard 1800-2012, Section 9.3.4, pg 178):
— endchecker (see 17.2)
— endclass (see 8.3)
— endclocking (see 14.3)
— endconfig (see 33.4)
— endfunction (see 13.4)
— endgroup (see 19.2)
— endinterface (see 25.3)
— endmodule (see 23.2.1)
— endpackage (see 26.2)
— endprimitive (see 29.3)
— endprogram (see 24.3)
— endproperty (see 16.2)
— endsequence (see 16.8)
— endtask (see 13.3)
in the verilog-mode.el, it looks like the named ends were considered but instead of auto-updating them, lines with named ends were totally ignored.
Before I try to get a solution to auto named ends (only for the above types of endings), I was like to know the reason for that specific @(unless ..)@ condition.
The reason I am looking into this is because I see a growing convention of using named ends instead of comments at the ends. Named ends can help catch a copy/paste mistake if the user had mismatch between the block name and end name.
Thanks.
The text was updated successfully, but these errors were encountered:
Author Name: Kaushal Modi
Original Redmine Issue: 1038 from https://www.veripool.org
Original Date: 2016-02-19
Hi,
I was leaning towards getting auto named ends functionality just like the auto endcomments functionality that we have right now.
Initially my thought was to add a defvar which would use ":" instead of "//" when auto inserting the named ends (instead of named comments).
That too would only happen for these endings (as per IEEE SystemVerilog Standard 1800-2012, Section 9.3.4, pg 178):
But looking at "this line":
verilog-mode/verilog-mode.el
Line 4661 in af5567b
Before I try to get a solution to auto named ends (only for the above types of endings), I was like to know the reason for that specific @(unless ..)@ condition.
The reason I am looking into this is because I see a growing convention of using named ends instead of comments at the ends. Named ends can help catch a copy/paste mistake if the user had mismatch between the block name and end name.
Thanks.
The text was updated successfully, but these errors were encountered: