Clarify that ISO Prolog means the Prolog General Core

[rotu]

The term "ISO Prolog" is expansive and suggests that Scryer may be ISO/IEC 13211-2 compliant. Remove this ambiguity.

[UWN]

Reject both changes. These changes just are the view of @rotu. The effort to comment these is significantly larger than the actual change.

[UWN]

You are abusing Scryer for your personal comments on the standard. Please do stick to identifying actual problems.

[rotu]

I'm making every effort here to be factual and respectful. ISO Modules are awesome and I would love to see them implemented!

You are abusing Scryer for your personal comments on the standard.

I don't mean to and I'm sorry that that's how anything has come across. I've striven to understand Scryer and ISO Prolog and I respect the hard work that has gone into both. This PR addresses an ambiguity that hopefully furthers both.

What in here is at all objectionable, and how can I make this PR better?

[UWN]

ISO Modules are awesome and I would love to see them implemented!

To be clear: You mean your reading of ISO modules. You do not mean the reading applied here in Scryer and which corresponds to many other systems.

[rotu]

To be clear: You mean your reading of ISO modules. You do not mean the reading applied here in Scryer and which corresponds to many other systems.

I mean an implementation of enough directives and features, to the extent where a meaningful program, using at least 2 modules, can run verbatim on multiple interpreters Prolog implementations.

I think you have that same vision in mind. I would like to take the conversation offline and understand what needs to happen, and by whom, to get there. Would you be available for a short chat?

[rotu]

I'm very much missing something here. Other Prolog systems make similar citations.

https://sicstus.sics.se/sicstus/docs/latest4/html/sicstus.html/ISO-Compliance.html#ISO-Compliance

SICStus Prolog is fully compliant with the International Standard ISO/IEC 13211-1 (PROLOG: Part 1—General Core) as augmented by Technical Corrigenda 1, 2 and 3.

https://eclipseclp.org/Specs/iso_conformity.html

ECLiPSe provides an implementation of Standard Prolog as defined in ISO/IEC 13211-1 (Information Technology, Programming Languages, Prolog, Part 1, General Core, 1995) and the technical corrigenda ISO/IEC 13211-1 TC1 (2007), TC2 (2012), and TC3 (2017, since ECLiPSe 7.0).

[rotu]

@mthom, @UWN Please suggest a wording so we can move this forward.

The posture toward ISO/IEC 13211-2 should be either:

1. It doesn’t apply to Scryer.
2. We implement it today and e.g. the missing colon_sets_calling_context Prolog flag is a functionality gap.
3. We aspire to implement it in the future and it belongs on the roadmap.