--- Quote Start ---
I think the Quartus error message help really says it all here!
Error (10172): Verilog HDL unsupported feature error at x.v(6): real variable data type values are not supported
Verilog HDL unsupported feature error at <location>: real variable data type values are not supported
--------------------------------------------------------------------------------
CAUSE: In a Verilog Design File (.v) at the specified location, you declared a real variable data type.
although verilog hdl supports real variable data types, this type is not supported in the quartus ii software. ACTION: Change the data type of the variable to something other than real.
--- Quote End ---
If the function were used after compilation time and active in the design itself, then I would understand Quartus II getting upset - but the fact of the matter is that each real function call I perform gets collapsed down to a constant, static value. In other words, to allow for reusable code and a greater number of built-time parameters, I want to use Quartus II as a fancy calculator. It is obviously capable of performing operations (at compile time) on real numbers. Quartus II should error only if:
- Non-static real values are being evaluated by a function
- A real is declared as a port input or output
Otherwise, it's just a macro - right? Even if you assign a real value to an array of wires, Verilog isn't strictly typed so it should just perform the conversion - right?
Honored Contributor
