Re: Unassigned carry-over issues for the LRM

From: Andrew Piziali <andy_at_.....>
Date: Tue Jul 14 2009 - 10:02:11 PDT
Darren, you wrote:

> Following on from yesterdays telecon, here is a list of carry-over
> topics from the last standardisation process which we might want to
> address in this standard. Please can people take a look and comment to
> the reflector in anticipation of a further discussion on what we do
> with them in a future telecon ...

> Issue 2763 - semicolons as separators

> The LRM always refers to semicolons as separators. It never
> specifically allows a semicolon following the last language element,
> as is found in much existing e code.

This should probably be addressed from the standpoint of null e language
elements.  For example, a null action is a valid element of a method and
is introduced by a pair of semicolons or a semicolon preceding the brace
that closes a method body.


-- 
        Andrew Piziali, <andy@piziali.dv.org>, +1-214-455-8577


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Received on Tue Jul 14 09:59:13 2009

This archive was generated by hypermail 2.1.8 : Tue Jul 14 2009 - 09:59:20 PDT