andr3/scyther
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

- The TMN protocol was wrongly reporting an error in the protocol. This

Browse Source 
turned out to be caused by an over-protective first-read detection.
This commit is contained in:
ccremers 2004-10-12 16:58:29 +00:00
parent d64badefdc
commit 487212a9f9
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
src/system.c
View File

@ -327,6 +327,10 @@ runsPrint (const System sys)
} }
//! Determine whether a term is sent or claimed, but not read first in a roledef //! Determine whether a term is sent or claimed, but not read first in a roledef
/**
* @returns True iff the term occurs, and is sent/claimed first. If this returns true,
* we have to prefix a read.
*/
int int
not_read_first (const Roledef rdstart, const Term t) not_read_first (const Roledef rdstart, const Term t)
{ {
@ -341,12 +345,8 @@ not_read_first (const Roledef rdstart, const Term t)
} }
rd = rd->next; rd = rd->next;
} }
globalError++; /* this term is not read or sent explicitly, which is no problem */
eprintf ("The term "); /* So we signal we don't have to prefix a read */
termPrint (t);
eprintf (" is not read or sent in some roledef.\n");
error ("Aborting.");
globalError--;
return 0; return 0;
} }