Consider the following module: :- module(foo, []). a. We get: ?- module_property(foo, exports(L)). L = []. ?- module_property(foo, exported_operators(L)). false. The exported_operators/1 property failing instead or returning empty list makes handling it cumbersome. Any reason to not behave the…

[image] pmoura: I do think that SWI-Prolog exports/1 and exported_operators/1 should be consistent and return an empty list when there are no exports to report. Pushed. If you think you can push several developers to do the same (or at least for the core features), I’m happy to support such …

Except for that is how it happens to be implemented, I guess not. Now I guess module_property/2 is not widespread, but if other systems would adopt it they might not have a notion of exporting operators (e.g., SICStus). My guess is that if you aim at portability you should anticipate on propertie…

YAP returns both predicates and operators when using the exports/1 property. SICStus Prolog doesn’t provide a module_property/2 predicate (and, as in YAP, operators are not local to modules). ECLiPSe provides instead a get_module_info/3 predicate with a raw_interface property, which returns a list w…

Module property exported_operators/1 fails instead of returning empty list

Help! Predicate

Topic		Replies	Views
Is it possible to export an operator from a unit test? Help!	0	365	January 14, 2022
Exporting predicate as an operator General	8	302	January 31, 2023
predicate_property(:Head, exported) returning false? General bug	7	115	April 21, 2025
Build list of predicates that can be exported from a module Nice to know	0	476	August 2, 2020
Use_module not importing all predicates Help!	28	1814	March 22, 2020

Module property exported_operators/1 fails instead of returning empty list

Related topics