From f01d637bb66ae172f849d0b6f26e231d335e8737 Mon Sep 17 00:00:00 2001
From: dgelessus <dgelessus@users.noreply.github.com>
Date: Mon, 9 Oct 2023 15:19:52 +0200
Subject: [PATCH] Use new printProlog method from theory mapping parser
This allows extending/modifying the Prolog term format for theory
mappings in the future.
---
de.prob.core/src/de/prob/eventb/translator/Theories.java | 9 +--------
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git a/de.prob.core/src/de/prob/eventb/translator/Theories.java b/de.prob.core/src/de/prob/eventb/translator/Theories.java
index 6df44f11..fef28e07 100644
--- a/de.prob.core/src/de/prob/eventb/translator/Theories.java
+++ b/de.prob.core/src/de/prob/eventb/translator/Theories.java
@@ -245,15 +245,8 @@ public class Theories {
private static void printMappings(Collection<OperatorMapping> mappings,
IPrologTermOutput pto) {
pto.openList();
- // Currently, we support only one kind of operator mapping, just tagging
- // an operator to indicate that an optimized ProB implementation should
- // be used. We do not invest any effort in preparing future kinds of
- // other operator mappings.
for (OperatorMapping mapping : mappings) {
- pto.openTerm("tag");
- pto.printAtom(mapping.getOperatorName());
- pto.printAtom(mapping.getSpec());
- pto.closeTerm();
+ mapping.printProlog(pto);
}
pto.closeList();
}
--
GitLab