Path: ...!weretis.net!feeder8.news.weretis.net!reader5.news.weretis.net!news.solani.org!.POSTED!not-for-mail From: Mild Shock Newsgroups: comp.lang.prolog Subject: Is old school mode directed compilation dead? (Was: thank you for the FLOPs) Date: Fri, 24 Jan 2025 17:57:17 +0100 Message-ID: References: <1b7ce2bd-722b-4c2e-b853-12fc2232752bn@googlegroups.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Fri, 24 Jan 2025 16:57:16 -0000 (UTC) Injection-Info: solani.org; logging-data="447885"; mail-complaints-to="abuse@news.solani.org" User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:128.0) Gecko/20100101 Firefox/128.0 SeaMonkey/2.53.20 Cancel-Lock: sha1:Z/Dgom/uVvVKSfHU92n7VuzTwP8= In-Reply-To: X-User-ID: eJwNwokRwDAIA7CVSAA7rMO3/wjtSa44KBoc5vsLxjFIVYyh7+OoLbFU6ZF1L8tmdlJXY+T1LtB+L6iGD0TEFSs= Bytes: 2569 Lines: 53 Hi, Just noticed that SICStus Prolog says that their mode declaration is a dummy declaration, does nothing. Now I tried whether I can force SWI Prolog to accept different manually compiled clauses: test1(X,Y) :- Y = j(C,D), g(C) = A, h(D) = B, f(A,B) = X. test2(X,Y) :- X = f(A,B), A = g(C), B = h(D), j(C,D) = Y. Difficult to archive in SWI-Prolog, since it orders unification on its own, test1/2 and test2/2 will behave the same, since they are essentially the same: /* SWI-Prolog 9.3.19 */ ?- listing(test1/2), listing(test2/2). test1(f(A, B), j(C, D)) :- A=g(C), B=h(D). test2(f(A, B), j(C, D)) :- A=g(C), B=h(D). But maybe not necessary since SWI-Prolog has an advanced instruction set and advanced Prolog logical variable representation? Bye Mild Shock schrieb: > Hi, > > Given that Scryer Prolog is dead. > This made me smile, traces of Scryer Prolog > > are found in FLOPs 2024 proceedings: > > 7th International Symposium, FLOPS 2024, > Kumamoto, Japan, May 15–17, 2024, Proceedings > https://www.cs.ox.ac.uk/jeremy.gibbons/flops2024.pdf > > So why did it flop? Missing garbage collection > in the Prolog System? Or did or is it to estimate > that ChatGPT will also kill Scryer Prolog? > > Or simply a problem of using Rust as the > underlying host language? > > Bye