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

From: Bresticker, Shalom <shalom.bresticker_at_.....>
Date: Wed Apr 29 2009 - 09:21:40 PDT
Hi, 

> > I prefer not to allow this explicitly. I think it is bad practice.
> 
> Why is it bad practice to eliminate redundancy and have a 
> single declaration for the type and kind of the data object?

That would be if the port declaration included only the port name.
However, if you say that the port declaration may include port attributes (data type, etc.), but you don't guarantee that this information will be used and the real attributes may be something else, that is something else entirely.


> > I prefer to try to word the LRM in such a way as to allow 
> it implicitly, between the lines.
> 
> I don't know how to write an implicit compiler that reads 
> between the lines.

You don't have to. It would come out automatically by implementing the LRM as specified. That does not mean that you have to tell the user explicitly that he can do that combination.

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.
Received on Wed Apr 29 09:29:49 2009

This archive was generated by hypermail 2.1.8 : Wed Apr 29 2009 - 09:30:53 PDT