Feature Request -- Comments
Hello,
at the moment i test sigasi 2.0. In sigasi 2.0 you have now the format command instead of the align command in sigasi 1.0. I had already posted this feature request in a former post, but for a better readability of the code i place my comments as followed:
if (s_startup_done = '0') then -- set status for i in 0 to c_61e0_number_of_channels-1 loop s_o_6152_status_word(i)(c_status_ipv_invalid) <= '1'; -- ipv is invalid s_o_6152_status_word(i)(c_status_reset_active) <= '1'; -- reset is set end loop; elsif(s_startup_done = '1' and s_startup_done_p1 = '0') then -- with rising edge of startup done for i in 0 to c_61e0_number_of_channels-1 loop s_o_6152_status_word(i)(c_status_ipv_invalid) <= '0'; -- clear ipv invalid s_o_6152_status_word(i)(c_status_reset_active) <= '0'; -- clear reset end loop; end if;
Now, when I use the format command the comments are placed directly behind the code
if(s_startup_done = '0') then -- when init of device is not finished set ipv status word for i in 0 to c_61e0_number_of_channels – 1 loop s_o_6152_status_word(i)(c_status_ipv_invalid) <= '1'; -- ipv is invalid s_o_6152_status_word(i)(c_status_reset_active) <= '1'; -- reset is set end loop;
elsif(s_startup_done = '1' and s_startup_done_p1 = '0') then -- with rising edge of startup done for i in 0 to c_61e0_number_of_channels – 1 loop s_o_6152_status_word(i)(c_status_ipv_invalid) <= '0'; -- clear ipv invalid s_o_6152_status_word(i)(c_status_reset_active) <= '0'; -- clear reset end loop;
end if;
Maybe you could implement that the comments will be placed at column position XX (the position could be defined anywhere), and if the written code is longer than position XX the comment is directly placed after the last character with one whitespace between.
Bernd
- Forums:
We already do this
Currently you can't change this value, it is always set to 40.
Making the formatter configurable will happen, but currently it isn't planned.
I've logged this as ticket:1945
Post new comment