Maude-help mailing list

["Skeirik, Stephen R" <skeirik2 AT illinois.edu>]

Hi Pierce,

Without seeing the file in question, there is little help we can offer on why 
it may have failed to parse.

As a general note, Maude syntax ignores all redundant whitespace (adding one 
or more spaces is equivalent to one space); the only way whitespace matters 
is when you have two tokens mashed together that should be separated, since 
they will get parsed as one.

Regards,
Stephen

-----Original Message-----
From: 
pdouglis AT perspectalabs.com
 
<pdouglis AT perspectalabs.com>
 
Sent: Tuesday, June 25, 2019 4:34 PM
To: 
maude-help AT lists.cs.illinois.edu
Subject: [[Maude-help] ] "No parse for input" after end of module

Hello,
I'm trying to load a module from a file into Maude, but I'm getting a "No 
parse for input" error with the red line with "*HERE*" pointing at the line 
underneath the "endom" where there is nothing (in fact, there isn't even 
another blank line at the end of the file). This parsing error isn't 
particularly helpful to me and I was hoping some of you might have an idea 
what's causing it. I already checked that the parentheses around (omod __ is 
... endom) are closed and all other parsing errors that had been found within 
the module before this have been fixed. Any guidance you could offer would be 
greatly appreciated.

Thanks,
Pierce