From 1d491d62c7135e74084382a75fc60bd12d900bb7 Mon Sep 17 00:00:00 2001 From: Pamela Dyer <pamela.dyer@uconn.edu> Date: Sat, 25 Sep 2021 09:59:03 -0700 Subject: [PATCH] Update models/Example36_Compiler1_ComponentReuse.mp, models/Example37_Compiler2_ComponentReuse.mp files --- models/Example36_Compiler1_ComponentReuse.mp | 4 ++-- models/Example37_Compiler2_ComponentReuse.mp | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/models/Example36_Compiler1_ComponentReuse.mp b/models/Example36_Compiler1_ComponentReuse.mp index 322e92b..04f261b 100644 --- a/models/Example36_Compiler1_ComponentReuse.mp +++ b/models/Example36_Compiler1_ComponentReuse.mp @@ -10,7 +10,7 @@ parser with lexical analyzer based on regular expression matching. It models the behavior of Lex/Yacc generated compiler’s front end. This model represents an architecture where lexer stores tokens in the intermediary data structure -before parser starts to access it, and Example 38 is a model +before parser starts to access it, and Example 37 is a model where parser works with the lexer interactively. The Lexer part models the behavior of a typical Lex machine. The behavior of Stack is integrated into Parser’s behavior. @@ -27,7 +27,7 @@ and the rest of the MP model. Interactions in MP descriptions (event grammar rules), and such adjustment can be done in a declarative fashion by coordinating the reusable MP code and the MP code under development. -Examples 37 and 38 show how it can be done using a model +Examples 36 and 37 show how it can be done using a model of a compiler. References: diff --git a/models/Example37_Compiler2_ComponentReuse.mp b/models/Example37_Compiler2_ComponentReuse.mp index fa81a3a..65eacd7 100644 --- a/models/Example37_Compiler2_ComponentReuse.mp +++ b/models/Example37_Compiler2_ComponentReuse.mp @@ -8,7 +8,7 @@ of interactions between components. Description: Examples 36 and 37 are models of a bottom-up parser with lexical analyzer based on regular expression matching. It models the behavior of Lex/Yacc generated -compiler’s front end. Example 37 represents an +compiler’s front end. Example 36 represents an architecture where lexer stores tokens in the intermediary data structure before parser starts to access it, and this is a model where parser works with the lexer interactively. @@ -26,7 +26,7 @@ and the rest of MP model. Interactions in MP (coordination operations) are separated from the behavior descriptions (event grammar rules), and such adjustment can be done in a declarative fashion by coordinating the reusable MP code -and the MP code under development. Examples 37 and 38 show +and the MP code under development. Examples 36 and 37 show how it can be done using a model of a compiler. References: -- GitLab