Re: [myhdl-list] Shadow signals

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

Christopher Felton wrote:
> On Tue, Jun 23, 2009 at 3:47 AM, Jan Decaluwe <ja...@ja...> wrote:
>> Basically I tried to address the problem that some of
>> you have struggled with: the inflexibility of MyHDL signals.
>> For example, the fact that signal slices don't behave
>> as signals.
>>
>> It's all documented here:
>>
>>    http://www.myhdl.org/doku.php/meps:mep-105
>>
>> Feedback welcome!
>>
>> Jan
> 
> I pulled the latest code from the repository this morning and was
> unable to check if a variable was a "Signal".  It looks like the
> "Signal" changed from a class to a function?

Yes, I turned it into a factory function. The existing implementation
was way to complex (i.e. using __new__ to construct different Signal
subclasses depending on constructor parameters. With the additional
Signal subclasses coming up, this was becoming really ugly.

I thought this would be an innocent change - I didn't anticipate
that a MyHDL user would ever need to test whether an object belongs
to the Signal class. Why do you need this?

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
    Analog design automation: http://www.mephisto-da.com
    World-class digital design: http://www.easics.com