Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.prolog > #14162
| From | Mild Shock <janburse@fastmail.fm> |
|---|---|
| Newsgroups | comp.lang.prolog |
| Subject | Re: A PIP classification scheme is needed (Was: DCG restrictions on the left-hand side [Novacore]) |
| Date | 2024-08-13 13:08 +0200 |
| Message-ID | <v9fer7$161th$1@solani.org> (permalink) |
| References | <v8bc1u$indc$1@solani.org> <v9f8dj$156vo$1@solani.org> <v9f8ll$15791$1@solani.org> |
More hot topics flowing in: - PIP 904: Partial strings and memory mapping Compact and shared char lists but memory mapped files. - PIP 601: DCG Defiinite clause grammars - PIP 602: PIO Clever DCGs over files using other than memory mapping. Mild Shock schrieb: > The PIP 903: Partial strings wasn't > so successful yet. Although pursued by > two Prolog systems, Scryer Prolog > > and Trealla Prolog, the results are > not a banger performance wise. Could > have to do with some DCG pipe dreams: > > /* Scryer Prolog 0.9.4-135 */ > ?- time((between(1,1000,_), data(X), json_chars(Y,X,[]), fail; true)). > % CPU time: 0.283s, 2_506_022 inferences > true. > > /* Trealla Prolog 2.55.19 */ > ?- time((between(1,1000,_), data(X), json_chars(Y,X,[]), fail; true)). > % Time elapsed 0.235s, 2568003 Inferences, 10.937 MLips > true. > > /* Dogelog Player for Java 1.2.1 */ > ?- time((between(1,1000,_), data(X), json_atom(Y,X), fail; true)). > % Zeit 40 ms, GC 0 ms, Lips 12502725, Uhr 13.08.2024 08:43 > true. > > /* SWI-Prolog 9.3.8 */ > ?- time((between(1,1000,_), data(X), atom_json_term(X,Y,[]), fail; true)). > % 44,998 inferences, 0.016 CPU in 0.006 seconds (281% CPU, 2879872 Lips) > true. > > Bye > > Mild Shock schrieb: >> . >> 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 | Find similar | Unroll 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