Checking modes of HAL programs

  • Authors:
  • Maric García De La Banda;Warwick Harvey;Kim Marriott;Peter J. Stuckey;Bart Demoen

  • Affiliations:
  • School of Computer Science & Software Engineering, Monash University, Australia (e-mail: mbanda@csse.monash.edu.au, marriott@csse.monash.edu.au) (e-mail: (wh@icparc.ic.ac.uk);School of Computer Science & Software Engineering, Monash University, Australia (e-mail: mbanda@csse.monash.edu.au, marriott@csse.monash.edu.au) (e-mail: (wh@icparc.ic.ac.uk);School of Computer Science & Software Engineering, Monash University, Australia (e-mail: mbanda@csse.monash.edu.au, marriott@csse.monash.edu.au) (e-mail: (wh@icparc.ic.ac.uk);Department of Computer Science & Software Engineering, University of Melbourne, Australia (e-mail: pjs@cs.mu.oz.au);Department of Computer Science, Catholic University Leuven, Belgium (e-mail: bmd@cs.kuleuven.ac.be)

  • Venue:
  • Theory and Practice of Logic Programming
  • Year:
  • 2005

Quantified Score

Hi-index 0.00

Visualization

Abstract

Recent constraint logic programming (CLP) languages, such as HAL and Mercury, require type, mode and determinism declarations for predicates. This information allows the generation of efficient target code and the detection of many errors at compile-time. Unfortunately, mode checking in such languages is difficult. One of the main reasons is that, for each predicate mode declaration, the compiler is required to appropriately re-order literals in the predicate's definition. The task is further complicated by the need to handle complex instantiations (which interact with type declarations and higher-order predicates) and automatic initialization of solver variables. Here we define mode checking for strongly typed CLP languages which require reordering of clause body literals. In addition, we show how to handle a simple case of polymorphic modes by using the corresponding polymorphic types.