Scryer Language / Machine / Runtime documentation

[jjtolton]

One thing that is excellent about Scryer is that since it is an ISO conforming Prolog (or perhaps that is redundant and I should just say "since it is Prolog") it is easy to ask questions about the language. However, there is very little information about Scryer itself in the ways that it is unique as a system -- it's more like clues scattered throughout scryer.pl, Power of Prolog, the discussion boards, the README, informal discussions, and comments in source code (and the source code itself).

A non-exhaustive list of things I'm referring to:

• The .scryerrc file (I had to read source code to figure out how to use this and where it goes, though I heard it mentioned in @triska 's videos)
• The library/module use_module path (e.g., is it the system path or something else? Is it configurable?)
• Creating/publishing/packaging modules
• Package management, if such a thing exists
• Usage of Scryer specific libraries (although most like advanced Prolog practitioners would be able to understand this by reading the source code)
• Updating Scryer regularly or how to know your version is up to date
• Semver concerns
• The toplevel controls that are specific to Scryer
• Scryer specific implementation details and caveats, for instance, compact representation of strings but (temporary) lack of GC on strings

Now that @aarroyoc has put together a documentation pages for us on scryer.pl, might be a great time to start adding that information!

Please feel free to use this topic to discuss things that might be good for both new and advanced users coming to Scryer in how to use the system most effectively (and idiomatically!)

Severability Clause: Even if you vehemently disagree with the inclusion of, say, "packaging modules" on this list, please know that the rest of the examples and the general point about the lack of centralized documentation regarding Scryer-specific functionalities still stands holds. @ me. 😉