Show simple item record

dc.contributor.authorCalvert, Kenneth L.en_US
dc.date.accessioned2005-06-17T18:04:57Z
dc.date.available2005-06-17T18:04:57Z
dc.date.issued1993en_US
dc.identifier.urihttp://hdl.handle.net/1853/6784
dc.description.abstractWe define a predicate transformer, in terms of which finite disjunctions of leads-to properties can be rewritten as single leads-to properties. Although disjunctions of leads-to properties do not typically arise naturally in progress specifications, an example shows how they may be introduced through the use of nested implications of leads-to properties; such implications allow subtle dependencies between a program's progress and that of its environment to be conveniently specified. After introducing the predicate transformer, which is called the "but-not-yet" operator, we show how to define a single leads-to property equivalent to a given disjunction of two leads-to properties. An alternative definition of the but-not-yet operator is shown to be equivalent to the first, and some properties of the operator are proved. Finally, the predicate transformer is generalized to any finite number of arguments.en_US
dc.format.extent149205 bytes
dc.format.mimetypeapplication/pdf
dc.language.isoen_US
dc.publisherGeorgia Institute of Technologyen_US
dc.relation.ispartofseriesCC Technical Report; GIT-CC-93-60en_US
dc.subjectPredicate transformers
dc.subjectLeads-to properties
dc.subjectDisjunctions
dc.subjectNested implications
dc.subjectBut-not-yet operator
dc.subjectLogical arguments
dc.subjectLogical operators
dc.subjectLogics of programs
dc.titleLeads-to Properties and the But-not-yet Operatoren_US
dc.typeText
dc.type.genreTechnical Report


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record