Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.prolog > #14160

A PIP classification scheme is needed (Was: DCG restrictions on the left-hand side [Novacore])

Show all headers | View raw

.
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'

Back to comp.lang.prolog | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

DCG restrictions on the left-hand side [Novacore] Mild Shock <janburse@fastmail.fm> - 2024-07-30 20:39 +0200
  Re: DCG restrictions on the left-hand side [Novacore] Mild Shock <janburse@fastmail.fm> - 2024-07-30 20:43 +0200
    Re: DCG restrictions on the left-hand side [Novacore] Mild Shock <janburse@fastmail.fm> - 2024-07-30 20:45 +0200
      Re: DCG restrictions on the left-hand side [Novacore] Mild Shock <janburse@fastmail.fm> - 2024-07-31 07:55 +0200
        Re: DCG restrictions on the left-hand side [Novacore] Mild Shock <janburse@fastmail.fm> - 2024-07-31 08:07 +0200
  post-N246 Read- and Write-Option variable_names/1 (Was: DCG restrictions on the left-hand side [Novacore]) Mild Shock <janburse@fastmail.fm> - 2024-08-10 20:20 +0200
    Re: post-N246 Read- and Write-Option variable_names/1 (Was: DCG restrictions on the left-hand side [Novacore]) Mild Shock <janburse@fastmail.fm> - 2024-08-10 20:33 +0200
      Is a PIP for Syntax extensions necessary? (Was; post-N246 Read- and Write-Option variable_names/1) Mild Shock <janburse@fastmail.fm> - 2024-08-11 00:02 +0200
        Re: Is a PIP for Syntax extensions necessary? (Was; post-N246 Read- and Write-Option variable_names/1) Mild Shock <janburse@fastmail.fm> - 2024-08-11 00:05 +0200
          Re: Is a PIP for Syntax extensions necessary? (Was; post-N246 Read- and Write-Option variable_names/1) Mild Shock <janburse@fastmail.fm> - 2024-08-11 00:16 +0200
            Re: Is a PIP for Syntax extensions necessary? (Was; post-N246 Read- and Write-Option variable_names/1) Mild Shock <janburse@fastmail.fm> - 2024-08-11 00:25 +0200
              Re: Is a PIP for Syntax extensions necessary? (Was; post-N246 Read- and Write-Option variable_names/1) Mild Shock <janburse@fastmail.fm> - 2024-08-11 14:46 +0200
  A PIP classification scheme is needed (Was: DCG restrictions on the left-hand side [Novacore]) Mild Shock <janburse@fastmail.fm> - 2024-08-13 11:18 +0200
    Re: A PIP classification scheme is needed (Was: DCG restrictions on the left-hand side [Novacore]) Mild Shock <janburse@fastmail.fm> - 2024-08-13 11:23 +0200
      Re: A PIP classification scheme is needed (Was: DCG restrictions on the left-hand side [Novacore]) Mild Shock <janburse@fastmail.fm> - 2024-08-13 13:08 +0200

csiph-web