sparkTechnology for engineering high-reliability s/w applications
2014langΣ=0 2014Version of this port present on the latest quarterly branch.
BROKEN: brutally fails test suite - with ICE DEPRECATED: Broken for more than 6 months This port expired on: 2016-09-30 IGNORE: is marked as broken: brutally fails test suite - with ICE
There is no maintainer for this port.
Any concerns regarding this port should be directed to the FreeBSD Ports mailing list via ports@FreeBSD.org
SPARK 2014 is a programming language and a set of verification tools
designed to meet the needs of high-assurance software development. SPARK
is based on Ada 2012, both subsetting the language to remove features that
defy verification, but also extending the system of contracts and aspects
to support modular, formal verification.
The new aspects support abstraction and refinement and facilitate deep
static analysis to be performed including information-flow analysis and
formal verification of an implementation against a specification.
SPARK is a much larger and more flexible language than its predecessor
SPARK 2005. The language can be configured to suit a number of application
domains and standards, from server-class high-assurance systems (such as
air-traffic management applications), to embedded, hard real-time,
critical systems (such as avionic systems complying with DO-178C Level A).
A major feature of SPARK is the support for a mixture of proof and other
verification methods such as testing, which facilitates the use of unit
proof in place of unit testing; an approach now formalized in DO-178C and
the DO-333 formal methods supplement. Certain units may be formally proven
and other units validated through testing.
WWW: http://www.spark-2014.org
Remove expired ports:
2016-09-30 math/why3-spark: Only useful for deprecated lang/spark
2016-09-30 lang/spark: Broken for more than 6 months
2016-09-30 math/alt-ergo-spark: Only useful for deprecate lang/spark
2016-09-30 security/nessus-libnasl: Abandoned, consider using OpenVAS
2016-09-30 security/nessus: Abandoned, consider using OpenVAS
2016-09-30 security/nessus-libraries: Abandoned, consider using OpenVAS
2016-09-30 security/nessus-plugins: Abandoned, consider using OpenVAS
lang/spark: extend expiration by 8 months
I'm still working on this port and I'm chasing down some runtime
segfaults which are not trivial to diagnose and fix.
Move math/why3-gpl => math/why3-spark
There are two reasons to rename this port.
1) Upstream never liked it and requested -spark be the suffix instead
2) An ongoing attempt to fix lang/spark may result in a number of slave
ports with a -spark suffix, so this keeps up consistency as all of
these ports only exist to support that port.
lang/spark: Mark BROKEN until further notice
While spark builds, gnatprove is getting murdered on the testsuite,
including emitting Internal Compiler Errors quite often. It's not
usable as is and needs more work.
Add new file lang/spark (will become run-depends for GPS)
SPARK 2014 is a programming language and a set of verification tools
designed to meet the needs of high-assurance software development. SPARK
is based on Ada 2012, both subsetting the language to remove features that
defy verification, but also extending the system of contracts and aspects
to support modular, formal verification.
The new aspects support abstraction and refinement and facilitate deep
static analysis to be performed including information-flow analysis and
formal verification of an implementation against a specification.
SPARK is a much larger and more flexible language than its predecessor
SPARK 2005. The language can be configured to suit a number of application
domains and standards, from server-class high-assurance systems (such as
air-traffic management applications), to embedded, hard real-time,
critical systems (such as avionic systems complying with DO-178C Level A).
A major feature of SPARK is the support for a mixture of proof and other
verification methods such as testing, which facilitates the use of unit
proof in place of unit testing; an approach now formalized in DO-178C and
the DO-333 formal methods supplement. Certain units may be formally proven
and other units validated through testing.
