Re: [myhdl-list] Block return values (myhdl.BlockError)

[Jan D. <ja...@ja...>]

On 13/05/16 16:45, Jos Huisken wrote:
> Jan Decaluwe <jan <at> jandecaluwe.com> writes:
>
>> I have nothing against collecting good ideas.
>>
>> However, for this specific feature, I am unconvinced
>> that the additional complexity is warranted. I may
>> change that opinion with future evidence - until
>> now it has only been brought up once as an alternative
>> possibility and does not seem enough.
>
> I didn't expect to raise such discussion ;-), and I guess we have to give
> it more thought. I have used all kinds of return values, next to Signals,
> especially in testbenches. The example I showed was a small part of a
> template based testbench+design which I will revisit, hopefully soon,
> with the current simplification.

For the record: the problem is limited to the return
values of blocks themselves. You will need to use
blocks for certain applications, but you are not
forced to use them for all modeling applications.

You can still use blocks within non-blocks and then
do whatever you want in terms of return values or
other sophisticated techniques.

The current Simulation API will remain available
to simulate such cases, in test benches or for
high-level modeling.

Blocks are merely intended to make hiearchy extraction
easier and much more robust, as needed for the important
sub-applications of conversion and signal tracing.

Jan


-- 
Jan Decaluwe - Resources bvba - http://www.jandecaluwe.com
   Python as a HDL: http://www.myhdl.org
   VHDL development, the modern way: http://www.sigasi.com
   Urubu, a static website CMS: http://urubu.jandecaluwe.com