Skip Navigation

The Computer Journal 1986 29(6):531-537; doi:10.1093/comjnl/29.6.531
© 1986 by British Computer Society
This Article
Right arrow Full Text (PDF)
Right arrow Alert me when this article is cited
Right arrow Alert me if a correction is posted
Services
Right arrow Email this article to a friend
Right arrow Similar articles in this journal
Right arrow Similar articles in ISI Web of Science
Right arrow Alert me to new issues of the journal
Right arrow Add to My Personal Archive
Right arrow Download to citation manager
Right arrow Search for citing articles in:
ISI Web of Science (2)
Right arrowRequest Permissions
Google Scholar
Right arrow Articles by Pandya, P.
Right arrow Articles by Joseph, M.
Right arrow Search for Related Content
Social Bookmarking
 Add to CiteULike   Add to Connotea   Add to Del.icio.us  
What's this?

A Structure-directed Total Correctness Proof Rule for Recursive Procedure Calls

P. Pandya * and M. Joseph

Computer Science Group, Tata Institute of Fundamental Research, Homi Bhabha Road, Bombay 400 005, India

Recursive procedures have been extensively used for a long time, yet it was only in 1977 that Sokolowski gave a proof rule for the total correctness of recursive procedure calls. Unfortunately, even for simple programs his rule requires the use of complex predicates that encode information about the depth of recursion. Thus the rule can be very difficult to use for practical programs. In this paper we propose a new rule for this purpose. This rule makes use of the structure of the recursion which is discovered by carrying out an interval analysis of the procedure call graph in the proof. Proofs using this rule are simpler to carry out, and it is shown that Sokolowski's rule is in fact a special case of the new rule.


Received March 1985.

* To whom correspondence should be addressed.

§ Computer Science Group, Tata Institute of Fundamental Research, Homi Bhabha Road, Bombay 400 005, India


Add to CiteULike CiteULike   Add to Connotea Connotea   Add to Del.icio.us Del.icio.us    What's this?




Disclaimer:
Please note that abstracts for content published before 1996 were created through digital scanning and may therefore not exactly replicate the text of the original print issues. All efforts have been made to ensure accuracy, but the Publisher will not be held responsible for any remaining inaccuracies. If you require any further clarification, please contact our Customer Services Department.