RE: Fw: Contributions (was Re: disallow distributed switch branches)

This discussion is a perfect example for one of
my comments I made earlier.  The tool/language
supposed to make the engineer's life easier, not
harder.

If you, the authors or experts of the language can't
remember these LRM details, how do you expect a newbie,
or a less experienced person to get their way through
the jungle of these (rather unintuitive) rules,
assumptions while learning to work with it?  Better
yet, how is that poor electrical engineer (***NOT***
computer scientist) engineer get his/her job done
in time when he/she keeps getting bogged down by
such language problems (limitations)?

I find myself going down the rat hole of way too many
language issues when I attempt to write new algorithms
giving me nightmares (literally) and delaying my job.

Please take these comments CONSTRUCTIVELY and SERIOUSLY
because my goal is not to make enemies, but to help
making the hardware programming world a better place
to live...  Plus, there are some companies who seem
to have figured out that user friendliness in their
tools helps making money, and in this competitive
market it will eventually be the customers who decide
who wins...

Thanks,

Arpad
=============================================================



-----Original Message-----
From: owner-verilog-ams@server.eda.org [mailto:owner-verilog-ams@server.eda.org] On Behalf Of Geoffrey.Coram
Sent: Friday, May 04, 2007 11:21 AM
To: Kevin Cameron
Cc: verilog-ams@server.eda.org
Subject: Re: Fw: Contributions (was Re: disallow distributed switch branches)

Kevin Cameron wrote:
> 
> > If there is already a current contribution on that branch,
> > then the new contrib would be an error!
> 
> Why? You can have a current contribution into a short.

It's an error because the LRM says so; it's a switch branch.

> > What do you mean moot?  The other form you show is an indirect
> > assignment, and the LRM presently contains restrictions against
> > using those along with direct contributions.
> >
> 
> That restriction only applies within a single analog block.
> Contributions via OOMR and ports are not restricted that way (the driver
> of the OOMR is a different block-instance).

At the end of Chapter 5 (5.3.2.2): "It is illegal to indirectly
assign to an external branch or contribute to an external branch
which has an indirect branch assignment."

-Geoffrey

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.