Forum Discussion

Altera_Forum's avatar
Altera_Forum
Icon for Honored Contributor rankHonored Contributor
14 years ago

Bad code, but no error, will settle for warning :)

This code compiles(!).

always @ (posedge clock ) begin

state <= NextState;

state <= state;

state <= 0;

end

Using the SignalTap it appears that state gets set to 0. Apparently its valid code. Is there a way to at least get a warning out of this?

Thank you,

Steve

4 Replies

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    14 years ago

    Why would you want a warning for perfectly valid code?

    The user has to take some responsibility!

    You may want to invest in a linting tool.
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    14 years ago

    I actually use that method when I want a default value on a signal. That way 'a' will always have a value even if I don't assign it in the if statement.

    always@(posedge clk)

    begin

    a <= 1'b0;

    if(something)

    begin

    a <= 1'b1;

    end

    else if(something else)

    begin

    <something that doesn't touch a>

    end

    end
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    14 years ago

    --- Quote Start ---

    I actually use that method when I want a default value on a signal. That way 'a' will always have a value even if I don't assign it in the if statement.

    end

    --- Quote End ---

    This seems like a good practice. Now I see the value of such a method.

    Thank you,

    Steve