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

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

On 10/05/16 11:45, Henry Gomersall wrote:
> On 10/05/16 10:32, Jan Decaluwe wrote:
>> I have considered this issue for some time now
>> and I have basically decided to leave the constraints
>> as they are, that is, blocks should only return
>> block and instantiator objects.
>
> I think your reasoning is sound.
>
> Do you object to alternative strategies for constructing Block
> operators? This could leave @block as the default usual case, with more
> esoteric cases handled by direct access to the construction of the Block
> object. This could allow the best of both worlds - simple default and
> arbitrary control if desired.

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.

My priority is moving forward with the simplifications
enabled by @block, and I believe there are several
much more relevant new features that these simplifications
will make possible.

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