PLIOError should not prevent weird errors, like

resource_errors (#36).
2009-06-12 13:46:44 -05:00 · 2009-06-12 13:46:44 -05:00 · 1005fa8abf
parent 303261b283
commit 1005fa8abf
1 changed files with 2 additions and 1 deletions
--- a/C/iopreds.c
+++ b/C/iopreds.c
@ -536,7 +536,8 @@ Yap_InitPlIO (void)
 static Int
 PlIOError (yap_error_number type, Term culprit, char *who)
 {
-  if (Yap_GetValue(AtomFileerrors) == MkIntTerm(1)) {
+  if (Yap_GetValue(AtomFileerrors) == MkIntTerm(1) ||
+      type == RESOURCE_ERROR_MAX_STREAMS /* do not catch resource errors */) {
    Yap_Error(type, culprit, who);
    /* and fail */
    return FALSE;