Zeus 3.97 Line comments bug

[gwgs]

Code: Select all

accept invfilename  {capslock}             // line comment not detected
[ok] begin                                 // line comment detected
   direct_output channel 2 invfilename     // line comment detected
   write channel 2  rtrim0(APTD0251.init)  // line comment not detected
end                                        // line comment detected
while [ok]                                 // not detected

Line comment set as //
From looking through other lines in my code I see that it isn't detecting line comments if any brackets have been used [] or () or {} at the end of a line there is a problem

Thanks

Grant

[jussij]

Hi Grant,

I suspect you have changed the document type (i.e. maybe added a pattern for example) and it is this change that is stopping the line comments from being detected

For example if you save this code to a test.txt file and then go to the document type for that text file and define // as a line comment you will see it paints correctly.

So something in the document type for this file is turning off the line comments for these lines

Cheers Jussi

[gwgs]

The settings are loaded under the default document type as I have several different extensions for the same language

[jussij]

The settings are loaded under the default document type

So there will be something configured Keywords section in the Default Document type that is overriding the detection of the line comments.

You can see this by defining a new document type with these line coments defined and you will see they will color correctly.

At least when I do that here, it does so for me

Cheers Jussi

[gwgs]

It used to work fine, and has for as long as I've used Zeus. It only changed with the 3.97 release, v3.96s and before all worked ok.

[jussij]

I'm not seeing the bug that you are describing and I suspect if you run the test that I described earlier you too will also see that this is still working.

Cheers Jussi

[gwgs]

Finally had a chance to look at this further. I checked the delimiter entry under Keywords, and found that it had a space at the end of the delimiter string. After removing that the line comments were detected correctly.

Grant

[jussij]

Hi Grant,

I checked the delimiter entry under Keywords, and found that it had a space at the end of the delimiter string. After removing that the line comments were detected correctly.

That is good news

I will make a change to trim the white space of the delimiter value, just to make this impossible to do in the future .

Cheers Jussi

[leo@lumanate.com]

Hi Jussi,

I just downloaded the editor (ver. 3.97) and tried it with Verilog file.
I noticed some line comments are not detected and some are.

Try this code (.v file):

Code: Select all

    //wire set_rd_bit_bar3; // LK 060509
    //wire set_rd_bit_bar4;
    //wire set_rd_bit_bar5;
    wire wr_dma_out_bar3; // LK 060809
    wire rd_dma_out_bar3;


    assign LED_4_lane  = cfg_c[6];		// LED0 on the Avnet V5LXT/SXT Development Board
    assign LED_8_lane  = cfg_c[7];		// LED1 on the Avnet V5LXT/SXT Development Board
    assign LED_test4  = ddr2_lock;		// LED0 on the Avnet V5LXT/SXT Development Board

  .trn_rd( trn_rd_c ),                     // I [63/31:0]
  .trn_rrem_n( trn_rrem_n_c ),             // I [7:0]
  .trn_rsof_n( trn_rsof_n_c ),             // I
  .trn_reof_n( trn_reof_n_c ),             // I
  .trn_rsrc_rdy_n( trn_rsrc_rdy_n_c ),     // I
  .trn_rsrc_dsc_n( trn_rsrc_dsc_n_c ),     // I
  .trn_rdst_rdy_n( trn_rdst_rdy_n_c ),     // O
  .trn_rerrfwd_n( trn_rerrfwd_n_c ),       // I
  .trn_rnp_ok_n( trn_rnp_ok_n_c ),         // O
  .trn_rbar_hit_n( trn_rbar_hit_n_c ),     // I [6:0]
  .trn_rfc_npd_av( trn_rfc_npd_av_c ),     // I [11:0]
  .trn_rfc_nph_av( trn_rfc_nph_av_c ),     // I [7:0]
  .trn_rfc_pd_av( trn_rfc_pd_av_c ),       // I [11:0]
  .trn_rfc_ph_av( trn_rfc_ph_av_c ),       // I [7:0]
  .trn_rfc_cpld_av( trn_rfc_cpld_av_c ),   // I [11:0]
  .trn_rfc_cplh_av( trn_rfc_cplh_av_c ),   // I [7:0]
  .trn_rcpl_streaming_n( trn_rcpl_streaming_n_c ), //O

Thanks,
-Leo.

[jussij]

Hi Leo,

This turns out to be a Zeus configuration bug.

To fix the bug, use the Options, Document Types menu and edit the Verilog Document Type. In the Keywords section edit the Delimiters string by removing the '/' character.

I will also make sure the Zeus installer setup details are also fixed.

Thanks for reporting this bug

Cheers Jussi

[leo@lumanate.com]

That worked!
Very cool!!!
Thank you,
-Leo.

[jussij]

In the Keywords section edit the Delimiters string by removing the '/' character.

It turns out the '/' character was not the problem in this case, but rather the delimiters string in the Verilog configuration contained a whitespace character.

By editing the configuration this latest version of Zeus remove the erant whitespace, fixing the issue.

So the '/' character can be re-entered as a delimiter

Cheers Jussi