k-user AT lists.cs.illinois.edu
Subject: K-user mailing list
List archive
- From: Eric Huber <echuber2 AT illinois.edu>
- To: Alex <alexdba AT gmail.com>
- Cc: k-user AT lists.cs.illinois.edu
- Subject: Re: [[K-user] ] Use of HOLE on rules
- Date: Tue, 18 Oct 2016 21:09:59 -0500
I believe that HOLE is deprecated and doesn't even lex as a keyword any more... the internal syntax uses "freezer" as you'll see if it halts with an incomplete evaluation, and you're supposed to handle the rules using strictness specifications now rather than HOLE. In the long run this is easier, but the documentation needs to be updated to reflect it. I think your best bet is to look for the most recently updated examples that ship in the K directory and study those.
Regards
Eric HuberOn Mon, Oct 17, 2016 at 8:02 AM, Alex <alexdba AT gmail.com> wrote:
and then plug it back to the context, but I get a compiler errorGreetings!I'm trying to use HOLEĀ to anticipate an evaluationsuggesting that HOLE is an ordinary variable:My attempts are based in examples, is the use of HOLE
[Error] Compiler: Found variable HOLE on right hand side of rule,
not bound on left hand side. Did you mean "?HOLE"?officially documented somewhere?Thanks!
- [[K-user] ] Use of HOLE on rules, Alex, 10/17/2016
- Re: [[K-user] ] Use of HOLE on rules, Eric Huber, 10/18/2016
Archive powered by MHonArc 2.6.19.