Re: [myhdl-list] Lists of signals now do appear in vcd file

[Christopher F. <chr...@gm...>]

On 6/27/2012 4:40 PM, Jan Decaluwe wrote:
> On 06/27/2012 08:14 PM, Christopher Felton wrote:
>> On 6/27/2012 12:15 PM, Jan Decaluwe wrote:
>>> I am considering to incorporate this feature more
>>> or less as per this patch.
>>>
>>> I don't want to create a different function - this
>>> could be a configuration of traceSignals.
>>>
>>> One question: should I make memory tracing optional?
>>> Or is it something that people just will always
>>> want to use when available?
>>>
>>> Jan
>>>
>>>
>>
>> I vote always on.
>>
>> If it were to be optional, I believe the use case is when modeling large
>> memories.  For a larger memory you might not want the overhead.  In this
>> case I would want a method to disable only for a particular LoS and not
>> all LoS.  My main use case for LoS is not to model RAM or ROM but for
>> modularity.
>
> I have implemented it such that it is on by default,
> and controlled by setting 'traceSignals.tracelists'.
> Only in 0.8-dev, this qualifies as a new feature instead
> of a bug.
>

Just wanted to say, this is a really nice feature!  Thanks
to Frederik and Jan D. for adding this feature!  It is nice,
in gtkwave you can create a group of the explicit LoS and
open/close (expand/hide) with a 'T'.

Regards,
Chris