-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error reporting , number_chars/2, installation problems. #192
Comments
Maybe a clarification for this table which was created in preparation of Cor.2. What you need to conform to is Section 0 and Section 2. In Section 1 the sorry state prior to Cor.2 is depicted.. |
@ichiban: one question on this: how do I go-wise update and recompile? ((For rust I say: |
@UWN Thank you very much for letting me know the problems! Note that $ git pull
Already up to date.
$ go install github.com/ichiban/prolog/cmd/1pl
$ $(go env GOPATH)/bin/1pl
Top level for ichiban/prolog (devel)
This is for testing purposes only!
See https://github.com/ichiban/prolog for more details.
Type Ctrl-C or 'halt.' to exit.
?- Alternatively, you can $ git pull
Already up to date.
$ go run cmd/1pl/main.go
Top level for ichiban/prolog (devel)
This is for testing purposes only!
See https://github.com/ichiban/prolog for more details.
Type Ctrl-C or 'halt.' to exit.
?- |
(It seems I am from the last century) Where is this directory, where I shall say
So I tried like:
Nowhere seems to be a path which ends with |
Here is the draft for the corrections of Cor.2 for the errors of |
@UWN I'm sorry for not being clear! To $ cd ~/src # Or anywhere you work with code.
$ git clone git@github.com:ichiban/prolog.git ichiban-prolog # Creates a working copy in ~/src/ichiban-prolog.
$ cd ichiban-prolog
$ git pull
Already up to date.
$ go install github.com/ichiban/prolog/cmd/1pl # Installs 1pl from this working copy. I think this is the fastest way to do Alternatively, you can fork The files under |
Or, how can I cleanly uninstall it? Such that I can just install it anew? I tried SO for this, but did not get any go-related good answer. Maybe I messed up something. But for other systems, everything is fine on github. |
Thank you, finally, I have everything in place. I will close this now, to make sure that issues remain related to one clear topic. |
#13:
Expected: type_error(list, [a|a]).
To make errors more uniform, it helps a lot to express them internally in two ways: must_be(Type, X) and can_be(Type, X). See e.g. library(error) of Scryer. In above case, the entire term has to be reported. with can_be(list, [a|a]) you get this automatically.
(Also note that a dot in a list is not recognized just as in #1)
The text was updated successfully, but these errors were encountered: