[m-rev.] for review: Define behaviour of string.to_char_list (and rev) on ill-formed sequences.

Zoltan Somogyi zoltan.somogyi at runbox.com
Wed Oct 23 10:55:45 AEDT 2019



On Wed, 23 Oct 2019 10:41:33 +1100 (AEDT), Julien Fischer <jfischer at opturion.com> wrote:
> While the inconsistency is not particularly desirable, I think that it's
> preferable to move to the names obsolete_{proc,pred}

Note that the current obsolete pragma cannot be simply renamed to obsolete_pred
for users. The former applies to both preds and funcs, while in userland the latter applies
only to preds. (Inside the compiler, we use "pred" in many places to mean "either pred or func",
as e.g. in pred_info.) We would need to replace obsolete with a pair of pragmas, obsolete_pred
and obsolete_func.

> as we should
> probably also support obsolescenece pragmas for other entities aside
> from predicates / procedures.

I would ask for a convincing use case for obsoleting non-code entities, but once users have
access to both obsolete_pred and obsolete_func, we would actually want to obsolete
"pragma obsolete" itself :-)

Zoltan.


More information about the reviews mailing list