I found that this was originally proposed in http://www.eda-stds.org/sv-bc/hm/0610.html as part of a general change to allow empty statements. But that proposal originally had 'always statement_or_null' as well. I did not find when 'always' was changed back to just 'statement' and not 'statement_or_null'. I did not find discussion on it. Shalom > -----Original Message----- > From: owner-sv-bc@server.eda.org > [mailto:owner-sv-bc@server.eda.org] On Behalf Of Bresticker, Shalom > Sent: Tuesday, January 29, 2008 2:23 PM > To: Jonathan Bromley; sv-bc > Subject: RE: [sv-bc] initial construct BNF > > Hi, > > > An empty "initial" is not crazy, and could easily be created by a > > parameterised macro in some situations. > > Yes, I agree it could, but it was not in 1364-2001 or even 1364-2005. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Tue Jan 29 06:03:46 2008
This archive was generated by hypermail 2.1.8 : Tue Jan 29 2008 - 06:04:23 PST