[Spark2014-discuss] [M122-037] specifying SPARK sources for analysis

Tucker Taft taft at adacore.com
Thu Mar 14 14:28:38 CET 2013

Our general conclusion was to use a mechanism more like suppress/unsuppress or assertion policy or warning off/on than using an aspect to control which features are permitted at any point. The aspect approach is too tied to declarations, whereas something which can be turned off and on at various levels of granularity. 

Sent from my iPhone

On Mar 14, 2013, at 8:01 AM, Arnaud Charlet <charlet at adacore.com> wrote:

>> Was there was some progress on this issue at the last design meetings?
>> Thanks in advance.
> In particular, one of the initial objections to proposals was that we
> needed to first list use cases before deciding on the syntax/solution.
> So, can someone (Andrew or Jon or Trevor?) summarize all the use cases
> identified so far, and summarize where we are in terms of proposal, if
> anything has been discussed?
> Note that I've reassigned this ticket to me, to converge/finalize this ticket
> since it's now time to wrap up all major language features at this point,
> we need to converge now and have a "feature freeze" in the RM occur soon,
> otherwise we will never be able to unblock other activities (tests and
> implementation) in time.
> Arno
> _______________________________________________
> Project spark2014 discuss mailing list
> discuss at spark2014.forge.open-do.org
> https://lists.forge.open-do.org/cgi-bin/mailman/listinfo/spark2014-discuss

More information about the Spark2014-discuss mailing list