Sujet : A PIP classification scheme is needed (Was: DCG restrictions on the left-hand side [Novacore])
De : janburse (at) *nospam* fastmail.fm (Mild Shock)
Groupes : comp.lang.prologDate : 13. Aug 2024, 10:18:44
Autres entêtes
Message-ID : <v9f8dj$156vo$1@solani.org>
References : 1
User-Agent : Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0 SeaMonkey/2.53.18.2
..
Hi,
SARS-CoV-2 variant are classified as variant under
monitoring (VUM), variant of interest (VOI)
and variant of concern (VOC).
How would we classify PIPs. Here is a list:
- PIP 701: Tasks
Stackfull and stackless cooperative cooroutines.
- PIP 702: Events
An event loop to “asyncify” file system access, network
access, queues, terminals, windowing systems, etc…
- PIP 801: Threads
Split off from Paulo Maura’s multi-threading document.
- PIP 801: Mutex
Split off from Paulo Maura’s multi-threading document.
- PIP 802: Message queues for multi-threading
Split off from Paulo Maura’s multi-threading document.
- PIP 803: Simpler queues not for multi-threading (@marco’s ?)
Other sources here.
- PIP 901: Embrace strings
String literal, unify, (==)/2 and (@<)/2
- PIP 902: Fully embrace strings
String is/2, (=:=)/2 and (<)/2
- PIP 903: Partial strings
Compact and shared char lists.
Bye
Mild Shock schrieb:
Guess how many newer Prolog systems allow this here:
?- [user].
p;q --> r.
true.
On the other hand SWI-Prolog disallows it:
?- [user].
p;q --> r.
ERROR: user://1:29:
ERROR: No permission to define dcg_nonterminal `p;q'