Maude-help mailing list

[Steven Eker <eker AT csl.sri.com>]

Loop mode uses the semantics of rewrite rather than frewrite or erewrite. In
principle it could be changed (but might break stuff) or a new eloop 
mode could be added.

But loop mode was an early hack to get Full Maude working; a cleaner 
solution would be to
use a MetaInterpreter but this code is unfinished, and is currently not 
a priority.

There is no way to do it without changing the C++ implementation.

Steven

On 2/27/13 3:44 AM, Lucian Bentea wrote:
> Hi everyone,
>
> I have a question regarding the "loop" command in Maude.
>
> As far as I understand, when running this command (or when the user 
> inputs some identifier), the rewriting of the loop state is 
> "internal", i.e., it does not allow messages to be exchanged with 
> external objects, as allowed by the "erewrite" command.
>
> Is there an easy solution to having a loop state that changes 
> according to external rewrites? Would this require changing the C++ 
> implementation for how the loop constructor [_,_,_] is handled?
>
> The reason why I find this useful, is that I think it would allow 
> language interpreters (including those based on Full Maude) to run 
> parallel algorithms on multi-core architectures. Please correct me if 
> I am wrong.
>
> I look forward to your opinion on this.
>
> Kind regards,
> Lucian
>
> _______________________________________________
> Maude-help mailing list
> Maude-help AT cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/maude-help