I disagree on this particular point. There is tons of perfectly good legacy design code that used the same loop index variable everywhere (except with nested loops), assuming there are no delays in the code. The problem started with always @*. As long as the user did not put the loop index into the sensitivity list, there were no problems. Regards, Shalom > 2) Using a module-level variable as the loop counter in a > procedural "for" loop is almost always a really stupid > thing to do. There is a huge risk of unwanted interaction > between loops in multiple processes - have you noticed how > every loop counter is called "i" or "j"? --------------------------------------------------------------------- Intel Israel (74) Limited This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Tue May 19 03:36:24 2009
This archive was generated by hypermail 2.1.8 : Tue May 19 2009 - 03:36:44 PDT