From jan@swi.psy.uva.nl  Thu Jun 15 14:00:56 2000
Received: from gollem.swi.psy.uva.nl (root@gollem [145.18.152.30])
	by swi.psy.uva.nl (8.9.3/8.9.3) with ESMTP id OAA06247;
	Thu, 15 Jun 2000 14:00:56 +0200 (MET DST)
Received: (from jan@localhost)
	by gollem.swi.psy.uva.nl (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id OAA21346;
	Thu, 15 Jun 2000 14:01:41 +0200
Date: Thu, 15 Jun 2000 14:01:41 +0200
Message-Id: <200006151201.OAA21346@gollem.swi.psy.uva.nl>
From: Jan Wielemaker <jan@swi.psy.uva.nl>
Subject: Re: read_term problem in 3.3.6?
To: Robb Shecter <shecter@darmstadt.gmd.de>, prolog@swi.psy.uva.nl
In-Reply-To: Robb Shecter's message of Thu, 15 Jun 2000 13:07:03 +0200
Phone: +31 - 20 - 525 6121

> read_term(Goal, [syntax_errors(Errs), variable_names(Vars)])
> 
> ...works just fine in version 2.8.x, but crashes in 3.3.6 with the
> error:
> 
> ERROR: Domain error: `read_option' expected, found
> `syntax_errors(_G329)'
> 
> The documentation for read_term doesn't seem to have changed -
> syntax_errors is still there.  Anybody know what the problem is?

The option is still there, but the arguments changed.  Bascially
use

	catch(read_term(Goal,
			[ syntax_errors(error),
			  variable_names(Vars)
			]), E, true),
	(   nonvar(E)
	->  <a syntax error>
	;   <read ok>
	).

This is compliant to the ISO standard.

	Regards --- Jan
	

