RE: Mantis 2593 about non-ANSI port declarations (Was: [sv-bc] Mantis 1111, omitting range on port declaration)

Hi, 

> > That would be if the port declaration included only the port name.
> 
> Yes, that's what I mean. I'm not convinced the following is 
> bad practice.
> 
>    input in1;
>    wire [5:0] in1;

As I said, that is different than saying you can put port attributes into the port declaration and then they may be ignored.

Regarding your suggestion, what I do not like about it is that you can not tell whether a port declaration of this type intends to just declare the port name or also the port type. It could be either-or. Today for the most part, port declarations contain the type information. It is true that tools do allow your example, but it is not common practice, and I would fire any engineer that would deliberately write this way.


> > It would come out automatically by implementing the LRM as 
> specified.
> 
> I'm not convinced that the draft LRM under ballot allows that 
> practice.

It was a debate among us during the discussion on 1111. IEEE rules say that you cannot rule a practice as non-conformant if the text can be interpreted that way, even if that is not the intended interpretation. That is the case here.

I am working on a re-formulation of the rules, I call it more a "declaration of principles" - a basis for a proposal, about the non-ANSI declarations. I don't think I'll manage to finish it today, it's already 8 PM and I still have some other things to do, so it will probably be tomorrow. Hopefully in the morning.

It also ties into Mantis 2395, which I think is a part of this.

By the way, does anyone understand the following sentence from the LRM?
"Using the non-ANSI header style with a port list followed by separate declarations for each port allows flexibility on the internal data to be passed through ports."

Thanks,
Shalom
---------------------------------------------------------------------
Intel Israel (74) Limited

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.


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