Understood. On the Ciao side, although we have no public release yet,
we have been fixing more than 100 previously failing conformance tests.
We'll be happy to notify you when it ships.
That effort is also the reason char_conversion/2 came up now: we
reached it in the course of fixing those cases. Almost everything up
to it we simply tried to correct against the standard;
char_conversion/2 was the one we paused on rather than implement
blindly, because its conforming behaviour for a Unicode reader was
unclear to us, which is why I raised it here. This may be relevant now
as well given the recent Unicode documents.
On deprecation, I agree. That is a next-version matter and we'll
leave it parked until then.
our considerations will be of relevance, when we are preparing a new
version of the standard. And then, a lot of things might have
changed. And we cannot predict them at all. Starting with ISO and
JTC1 rules. Discussing these currently here will pretty much lead to
nothing concrete. Also, comparisons to other working groups are
pretty difficult, since we have stakeholders that have not adopted the
standard in so many areas within 31 years. This is not the case in
e.g. WG14.
For the moment, we have very concrete work to do that affect
programmers in a much stronger way than to this one aspect you seem
more interested in.
1st syntax-conformity
2nd built-in conformity
3rd the Prolog prologue
and much more.
In all of these areas it is absolutely vital to have concrete
implementations that can be compared to each other and to the
specifications rigorously. Just producing documents without concrete
implementations isn't useful.
_______________________________________________
Prolog-standard mailing list -- prolog-standard@software.imdea.org
To unsubscribe send an email to prolog-standard-leave@software.imdea.org
--
Jose