Re: [myhdl-list] It should be possible to use a @process decorator wherever you can use @always

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

On 06/02/2011 09:27 AM, Günter Dannoritzer wrote:
> On 02.06.2011 08:55, Angel Ezquerra wrote:
> ...
>>
>> I am all for simple software an libraries, but I would say that this
>> addition would hardly make MyHDL more complex. Everything could stay
>> the same. After all it would just be a matter of doing:
>>
>> process = always
>> process_comb = always_comb
> ...
>
>> From the stand point of implementation it is simple, but how about from
> the standpoint of users?
>
> Think about a new user who is not familiar with any HDL and you explain
> her she can use either always or process to achieve that?
>
> How would that compare to learning a new programming language and the
> manual tells you that you can create i.e. classes with the keyword
> 'class' or if you wish also with the keyword 'klasse'.
>
> In my opinion that would be very confusing for me if I learn a language new.

I fully agree with that.

There may sometimes be a good reason to change a name in
favor of another one. However, I believe there should always be one
clearly preferred one, and one clearly deprecated one that
will be phased out over time.

Defining equivalent aliases is a no-go. It is bound to create much
more confusion than it would solve. I don't know of an example of a
software language that does so, for good reasons.

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