Re: Inconsistency between simulation and conversion

On Thu, Apr 28, 2016 at 7:12 AM, Samuele Disegna <[email protected]> wrote:

> On Thu, Apr 28, 2016 at 1:47 PM, Henry Gomersall <[email protected]> wrote:
>
>> On 28/04/16 07:54, Nicolas Pinault wrote:
>> > When using this statement "counter.next += 1" I get an error when
>> > converting my design to VHDL :
>> >
>> > myhdl.ConversionError: in file
>> > Z:\myHDL_Tests\NoiseFilter\src\noise_filter.py, line 51:
>> >     Not supported: Augmented signal assignment
>> >
>> > This makes sense.
>> > However, this same statement does not trig any error when simulating the
>> > design.
>> > Is this the intended behaviour ?
>> >
>>
>> Incrementing .next is a slightly odd thing to want to do,
>
>
> I would remove slightly to the sentence :).
> You are supposed to do "counter.next = counter+1" and not "counter.next =
> counter.next+1"
>
> Simulation in MyHDL is just execution of your code and you are allowed to
> do nasty things!
>
> Samuele
>

Absolutely, well stated.  We shouldn't increment the "next" but
assigning "next" to "current (val) + 1".  The augmented does't make
sense.

Regards,
Chris

------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z

_______________________________________________
myhdl-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/myhdl-list