gEDA-user: order of defparam vs. #(.) parameters in icarus

[Matt Ettus <boyscout@xxxxxxxxx>]

In some Xilinx models, they make instantiations like this:

block instance(ports);
defparam instance.param=VALUE


This normally works ok.  The problem is that inside the block,
generate statements are being used which are dependent on the value of
the parameter.  What appears to be happening is that the block is
instantiated, and before the defparam line is "executed", the
decisions are made with the default value of the parameter.

Is this a bug in Icarus or in the Xilinx models?

I can send an example that illustrates this if necessary.

Thanks,
Matt


_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user