What is wrong with the following code fragment?
always@(A or C)
D = A & C;
always@(posedge clock)
if (B) E

Question

What is wrong with the following code fragment? 
 always@(A or C) 
     D = A & C; 
 always@(posedge clock) 
      if (B) E <= C;

Accepted Answer

Nothing is wrong with this code fragment

Answer

The else is missing and unintentional latches are implied.

Answer

D should not be assigned like this.  Unbuildable “wired-or” logic is implied

Answer

C is missing from the second sensitivity list

Answer

Non blocking assignment should be used to obtain expected functionality

Crowdly