| Publications of year 1991 |
| Books and proceedings |
@Proceedings{df91,
title = {Proceedings of ICLP'91 Workshop on Logic Programming Environments},
year = {1991},
editor = {M. Ducassé and G. Ferrand},
month = {June},
note = {Technical Report, University of Orléans, France, LIFO N 91-61}
}
| Articles in journal or book chapters |
| Opium is an extensible debugging environment for PROLOG providing high-level debugging facilities for programmers and debugging experts. In the design of debuggers there are two tasks which are often mixed, extraction and analysis of debugging information. The aim of the extraction task is to collect the whole debugging information so that users do not miss any important information about their program. On the other hand, the aim of the analysis task is to restrict in an accurate way the amount of debugging information shown to the user so that the latter has to examine only the relevant parts. This task clearly depends on the debugging situation and, to our point of view, there is no general restriction which can be done a priori. However, the two tasks are usually mixed and hard-coded, the result is that not enough relevant information and too much useless information is displayed. In Opium the two tasks are clearly separated. The extraction module collects the whole debugging information (execution trace and program source) which is then available for the analysis module. The presentation concentrates on the analysis module, discussing the main aspects of Opium: programmability, high-level debugging, extensibility mechanisms, meta-debugging, support for end-users and debugging experts. |
@Article{de91d,
author = {M. Ducassé and A.-M. Emde},
title = {Opium: a debugging environment for {Prolog} development and debugging research},
journal = {ACM Software Engineering Notes},
year = {1991},
volume = {16},
number = {1},
pages = {54-59},
month = {January},
note = {Demonstration presented at the Fourth Symposium on Software Development Environments},
keywords = {demo},
abstract = {Opium is an extensible debugging environment for PROLOG providing high-level debugging facilities for programmers and debugging experts. In the design of debuggers there are two tasks which are often mixed, extraction and analysis of debugging information. The aim of the extraction task is to collect the whole debugging information so that users do not miss any important information about their program. On the other hand, the aim of the analysis task is to restrict in an accurate way the amount of debugging information shown to the user so that the latter has to examine only the relevant parts. This task clearly depends on the debugging situation and, to our point of view, there is no general restriction which can be done a priori. However, the two tasks are usually mixed and hard-coded, the result is that not enough relevant information and too much useless information is displayed. In Opium the two tasks are clearly separated. The extraction module collects the whole debugging information (execution trace and program source) which is then available for the analysis module. The presentation concentrates on the analysis module, discussing the main aspects of Opium: programmability, high-level debugging, extensibility mechanisms, meta-debugging, support for end-users and debugging experts. }
}
| Conference articles |
| We propose a new implementation of logic programming with higher-order terms. In order to illustrate the properties of our implementation, we apply the coding of lists as functions to the context of logic programming. As a side-effect, we show that higher-order unification is a good tool for manipulating the function-lists. It appears that the efficiency of the program thus obtained relies critically upon the implementation of higher-order operations (unification and reduction). In particular, we show that a good choice for data-structures and reduction strategy yields a linear naïve reverse. |
@InProceedings{brisset:naivereverse:iclp:91,
author = {P. Brisset and O. Ridoux},
title = {Naïve Reverse Can Be Linear},
booktitle = {8th Int. Conf. Logic Programming},
editor = {K. Furukawa},
publisher = {MIT Press},
comment = {Paris, France},
pages = {857--870},
year = 1991,
abstract = {We propose a new implementation of logic programming with higher-order terms. In order to illustrate the properties of our implementation, we apply the coding of lists as functions to the context of logic programming. As a side-effect, we show that higher-order unification is a good tool for manipulating the function-lists. It appears that the efficiency of the program thus obtained relies critically upon the implementation of higher-order operations (unification and reduction). In particular, we show that a good choice for data-structures and reduction strategy yields a linear naïve reverse.},
keywords = {LambdaProlog, implementation, function-lists, higher-order unification.},
url = {ftp://ftp.irisa.fr/local/lande/pbor-iclp91.ps.Z}
}
| Opium is a system for analysing and debugging Prolog programs. Its kernel comprises an execution tracer and a programming language with a full set of primitives for trace and source analysis. In this paper we show the power of Opium for supporting abstract views of Prolog executions. Abstract views give high-level points of view about the execution. They filter out irrelevant details; they restructure the remaining information; and they compact it so that the amount of information given at each step has a reasonable size. The examples of abstract views given in the following are a goal execution profile, some data abstractions, an instantiation profile, a failure analysis and a kind of explanation for an expert system written in Prolog. |
@InProceedings{duc91c,
author = {M. Ducassé},
url = {ftp://ftp.irisa.fr/local/lande/md-ilps91.ps.gz},
title = {Abstract views of {Prolog} executions in {Opium}},
booktitle = {Proceedings of the International Logic Programming Symposium},
editor = {V. Saraswat and K. Ueda},
address = {San Diego, USA},
year = {1991},
month = {October},
publisher = {MIT Press},
pages = {18-32},
location = {was IR-LP-31-28},
abstract = {Opium is a system for analysing and debugging Prolog programs. Its kernel comprises an execution tracer and a programming language with a full set of primitives for trace and source analysis. In this paper we show the power of Opium for supporting abstract views of Prolog executions. Abstract views give high-level points of view about the execution. They filter out irrelevant details; they restructure the remaining information; and they compact it so that the amount of information given at each step has a reasonable size. The examples of abstract views given in the following are a goal execution profile, some data abstractions, an instantiation profile, a failure analysis and a kind of explanation for an expert system written in Prolog. }
}
| Internal reports |
@TechReport{de91,
author = {M. Ducassé and A.-M. Emde},
url = {ftp://ftp.ecrc.de/pub/eclipse/doc/dvi/opium-manual.ps.Z},
title = {A High-level Debugging Environment for {Prolog}. {Opium} User's Manual},
institution = {ECRC},
number = {TR-LP-60},
type = {Technical Report},
month = {May},
year = {1991}
}
This material is presented to ensure timely dissemination of scholarly and technical work. Copyright and all rights therein are retained by authors or by other copyright holders. All person copying this information are expected to adhere to the terms and constraints invoked by each author's copyright. In most cases, these works may not be reposted without the explicit permission of the copyright holder.
Les documents contenus dans ces répertoires sont rendus disponibles par les auteurs qui y ont contribué en vue d'assurer la diffusion à temps de travaux savants et techniques sur une base non-commerciale. Les droits de copie et autres droits sont gardés par les auteurs et par les détenteurs du copyright, en dépit du fait qu'ils présentent ici leurs travaux sous forme électronique. Les personnes copiant ces informations doivent adhérer aux termes et contraintes couverts par le copyright de chaque auteur. Ces travaux ne peuvent pas être rendus disponibles ailleurs sans la permission explicite du détenteur du copyright.
This document was translated from BibTEX by bibtex2html