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

Groups > comp.lang.javascript > #124280 > unrolled thread

ANN: Dogelog Player 1.1.6 (HTTP Client)

Back to article view | Back to comp.lang.javascript

Contents

  ANN: Dogelog Player 1.1.6 (HTTP Client) Mild Shock <janburse@fastmail.fm> - 2024-03-07 18:10 +0100
    Re: ANN: Dogelog Player 1.1.6 (HTTP Client) Mild Shock <janburse@fastmail.fm> - 2024-03-10 19:09 +0100
      Re: ANN: Dogelog Player 1.1.6 (HTTP Client) Mild Shock <janburse@fastmail.fm> - 2024-03-10 23:49 +0100
        Re: ANN: Dogelog Player 1.1.6 (HTTP Client) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-11 00:49 +0000
          Re: ANN: Dogelog Player 1.1.6 (HTTP Client) Mild Shock <janburse@fastmail.fm> - 2024-03-11 09:06 +0100
            Re: ANN: Dogelog Player 1.1.6 (HTTP Client) Mild Shock <janburse@fastmail.fm> - 2024-03-11 09:07 +0100
              Re: ANN: Dogelog Player 1.1.6 (HTTP Client) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-11 20:46 +0000
                Re: ANN: Dogelog Player 1.1.6 (HTTP Client) Mild Shock <janburse@fastmail.fm> - 2024-03-12 00:19 +0100
                  Re: ANN: Dogelog Player 1.1.6 (HTTP Client) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-12 00:43 +0000
                    Re: ANN: Dogelog Player 1.1.6 (HTTP Client) Mild Shock <janburse@fastmail.fm> - 2024-03-13 02:05 +0100
                      Re: ANN: Dogelog Player 1.1.6 (HTTP Client) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-03-13 02:28 +0000
                        Re: ANN: Dogelog Player 1.1.6 (HTTP Client) Mild Shock <janburse@fastmail.fm> - 2024-03-13 12:54 +0100
                          Re: ANN: Dogelog Player 1.1.6 (HTTP Client) Mild Shock <janburse@fastmail.fm> - 2024-03-13 13:01 +0100
      Re: ANN: Dogelog Player 1.1.6 (HTTP Client) Mild Shock <janburse@fastmail.fm> - 2024-03-13 02:06 +0100
    Re: ANN: Dogelog Player 1.1.6 (HTTP Client) Mild Shock <janburse@fastmail.fm> - 2024-03-23 16:43 +0100
      Re: ANN: Dogelog Player 1.1.6 (HTTP Client) John Harris <niam@jghnorth.org.uk.invalid> - 2024-03-24 10:39 +0000
        Re: ANN: Dogelog Player 1.1.6 (HTTP Client) Mild Shock <janburse@fastmail.fm> - 2024-03-24 12:23 +0100
          Re: ANN: Dogelog Player 1.1.6 (HTTP Client) John Harris <niam@jghnorth.org.uk.invalid> - 2024-03-26 11:06 +0000
            Re: ANN: Dogelog Player 1.1.6 (HTTP Client) Mild Shock <janburse@fastmail.fm> - 2024-03-26 20:21 +0100
              Re: ANN: Dogelog Player 1.1.6 (HTTP Client) Mild Shock <janburse@fastmail.fm> - 2024-03-26 20:25 +0100
              Re: ANN: Dogelog Player 1.1.6 (HTTP Client) John Harris <niam@jghnorth.org.uk.invalid> - 2024-03-27 14:12 +0000
                Re: ANN: Dogelog Player 1.1.6 (HTTP Client) Mild Shock <janburse@fastmail.fm> - 2024-03-27 23:52 +0100
                  Re: ANN: Dogelog Player 1.1.6 (HTTP Client) Mild Shock <janburse@fastmail.fm> - 2024-03-27 23:56 +0100
                Re: ANN: Dogelog Player 1.1.6 (HTTP Client) Mild Shock <janburse@fastmail.fm> - 2024-03-28 00:07 +0100
                  Re: ANN: Dogelog Player 1.1.6 (HTTP Client) Mild Shock <janburse@fastmail.fm> - 2024-03-28 00:16 +0100
                    Re: ANN: Dogelog Player 1.1.6 (HTTP Client) Mild Shock <janburse@fastmail.fm> - 2024-03-28 00:21 +0100
      Re: ANN: Dogelog Player 1.1.6 (HTTP Client) Mild Shock <janburse@fastmail.fm> - 2024-04-02 01:18 +0200

Page 2 of 2 — ← Prev page 1 [2]

#124330

On 26/03/2024 19:21, Mild Shock wrote:
> Fucking liar, look again. Like hier:
> 
> 
> 4.1 Folder "util"
> Section "meta"

   <snip>

Section "meta" has 13 lines of text. Tell us which ones describe a data 
structure. And no, "cross_loading/1" is not a description.

Your JavaScript code includes some form of garbage collection. Has that 
influenced the data structures ?

   John

[toc] | [prev] | [next] | [standalone]

#124331

Do you have even the slightest clue of logic programming?

Dogelog Player is a Prolog system 100% written
in Prolog itself. Where do you expect the data to
be stored? For your informaton moron, this here:

cross_loading/1

Is a so called predicate indicator (PI), giving
you the formation of the predicate name and predicate
arity. So the data model in very shortened relational
notation is this here:

cross_loadeing(_)

Where:

cross_loading: The table name

_: The single column.

Hope this helps. More accademic names for data inside
Prolog are, the so called extensional database (EDB):

The set of facts is called the extensional
database or EDB of the Datalog program
https://en.wikipedia.org/wiki/Datalog

John Harris schrieb:
> On 26/03/2024 19:21, Mild Shock wrote:
>> Fucking liar, look again. Like hier:
>>
>>
>> 4.1 Folder "util"
>> Section "meta"
> 
>    <snip>
> 
> Section "meta" has 13 lines of text. Tell us which ones describe a data 
> structure. And no, "cross_loading/1" is not a description.
> 
> Your JavaScript code includes some form of garbage collection. Has that 
> influenced the data structures ?
> 
>    John
> 
> 

[toc] | [prev] | [next] | [standalone]

#124332

I mean I repeat in every post and blog I make
about Dogelog Player that it is written in 100%
Prolog itself. This means it uses Prolog for its

own data. You call these posts nauseating. I call
you a complete fucking moron with blistering
herpes furuncle on top of your neck.

Gets some brain cells idiot. Its should be also
explained in the docu what it means that Dogelog
Player is 100% written in Prolog itself.

But I do not intend make a citation now.

Just get lost and don't waste everybodies time.

Mild Shock schrieb:
> Do you have even the slightest clue of logic programming?
> 
> Dogelog Player is a Prolog system 100% written
> in Prolog itself. Where do you expect the data to
> be stored? For your informaton moron, this here:
> 
> cross_loading/1
> 
> Is a so called predicate indicator (PI), giving
> you the formation of the predicate name and predicate
> arity. So the data model in very shortened relational
> notation is this here:
> 
> cross_loadeing(_)
> 
> Where:
> 
> cross_loading: The table name
> 
> _: The single column.
> 
> Hope this helps. More accademic names for data inside
> Prolog are, the so called extensional database (EDB):
> 
> The set of facts is called the extensional
> database or EDB of the Datalog program
> https://en.wikipedia.org/wiki/Datalog
> 
> John Harris schrieb:
>> On 26/03/2024 19:21, Mild Shock wrote:
>>> Fucking liar, look again. Like hier:
>>>
>>>
>>> 4.1 Folder "util"
>>> Section "meta"
>>
>>    <snip>
>>
>> Section "meta" has 13 lines of text. Tell us which ones describe a 
>> data structure. And no, "cross_loading/1" is not a description.
>>
>> Your JavaScript code includes some form of garbage collection. Has 
>> that influenced the data structures ?
>>
>>    John
>>
>>
> 

[toc] | [prev] | [next] | [standalone]

#124333

John Harris schrieb:
> Your JavaScript code includes some form of garbage 
> collection. Has that influenced the data structures ?

There is a long thread about the early Garbage Collection
of Dogelog Player in comp.lang.python. Especially whether
it can be made fast, with useful input from a few
Pythonistas.

Then I post regularly about the evolution of the GC
of Dogelog Player. It was just posted a few days ago,
when you were still on your silly tangent that my

posts are nauseating. Now you are asking stuff, that
I am anyway posting about. Whats is wrong with you?
Do you have a PhD in being the most stupid person

on this planet? See here, few days ago,
to be exact 5 days ago:

Mild Shock schrieb 23.03.2024, 16:43:
 >
 > Dogelog Player is a Prolog system that features
 > a generational garbage collector scheme and a
 > change_arg/3 primitive built-in. So far the two
 > didn’t go together and we had to use a cludge.
 > With the upcoming release we provide a proper
 > solution based on marking write-barriers.
 >
 > Our remembered set on the variable binding trail
 > has the benefit that it can reduce itself during
 > backtracking. By adopting conductor variables, i.e.
 > instantiated variables that are not trailed, from
 > formerly Jekejeke Prolog, we could recreate a
 > similar benefit for Dogelog Players change_arg/3.
 >
 > See also:
 >
 > Marking Write-Barriers for Dogelog Player
 > https://twitter.com/dogelogch/status/1771559896741192186
 >
 > Marking Write-Barriers for Dogelog Player
 > https://www.facebook.com/groups/dogelog

[toc] | [prev] | [next] | [standalone]

#124334

Of course before reading anything about Dogelog Player
you have to start with the reference section also known
as bibliography, which is found at the end of PDF here:

Dogelog Player Host Version 1.1.5, December 17, 2023
https://www.novacuor.ch/doctab/rscsrv/docs/17_host/package.pdf

You need to first understand the below things before
you dig and put your nose into Dogelog Player:

[1] ISO (1995): Prolog, Part 1: General Core,
International Standard ISO/IEC 13211-1, First Edition, 1995-06-01
http://www.iso.org/standard/21413.html

[2] Clocksin, W. (1983): A portable Prolog compiler, Logic Programming 
Workshop, Albufeira Portugal, January 1983
http://www.softwarepreservation.org/projects/prolog/lisbon/lpw83/p74-Bowen.pdf

[3] Carlson, M. et al. (1988): Garbage collection for Prolog based on 
WAM. Communications of the ACM 31, 6, 719–740, June 1988
http://dl.acm.org/doi/10.1145/62959.62968

Dogelog Player implements variants of [1], [2] and [3].
SWI-Prolog also implementes [3], but it doesn't implement
the generational part of [3]. Recently I managed to also

implement the generatioal part of [3] via some coloring
approach. If I am not mistaken you find a blog about it
also announced here and somewhere on medium.com.

And most recently I removed a cludge from change_arg/3
also related to [3]. And according blog I also announced
here to be exact 5 days ago. Its also on medium.com.

Maybe you need medium.com membership to be able to read it.

Mild Shock schrieb:
> John Harris schrieb:
>> Your JavaScript code includes some form of garbage collection. Has 
>> that influenced the data structures ?
> 
> There is a long thread about the early Garbage Collection
> of Dogelog Player in comp.lang.python. Especially whether
> it can be made fast, with useful input from a few
> Pythonistas.
> 
> Then I post regularly about the evolution of the GC
> of Dogelog Player. It was just posted a few days ago,
> when you were still on your silly tangent that my
> 
> posts are nauseating. Now you are asking stuff, that
> I am anyway posting about. Whats is wrong with you?
> Do you have a PhD in being the most stupid person
> 
> on this planet? See here, few days ago,
> to be exact 5 days ago:
> 
> Mild Shock schrieb 23.03.2024, 16:43:
>  >
>  > Dogelog Player is a Prolog system that features
>  > a generational garbage collector scheme and a
>  > change_arg/3 primitive built-in. So far the two
>  > didn’t go together and we had to use a cludge.
>  > With the upcoming release we provide a proper
>  > solution based on marking write-barriers.
>  >
>  > Our remembered set on the variable binding trail
>  > has the benefit that it can reduce itself during
>  > backtracking. By adopting conductor variables, i.e.
>  > instantiated variables that are not trailed, from
>  > formerly Jekejeke Prolog, we could recreate a
>  > similar benefit for Dogelog Players change_arg/3.
>  >
>  > See also:
>  >
>  > Marking Write-Barriers for Dogelog Player
>  > https://twitter.com/dogelogch/status/1771559896741192186
>  >
>  > Marking Write-Barriers for Dogelog Player
>  > https://www.facebook.com/groups/dogelog

[toc] | [prev] | [next] | [standalone]

#124335

So move your lazy ass become member of twitter
or facebook, and also member of medium and qiita. I won't
post full blog articles here on comp.lang.javascript,

also not on comp.lang.python, or any other news group.
I only post a short notice in news groups, when a new
article is out of the oven. And don't post full articles.

Also articles might cover more than the manuals, since
articles are reports from the Dogelog Player research Lab.
 From steaming hot Lab logic programming experiments.

Even more hotter than boring Soufflé that needs types.

Mild Shock schrieb:
> 
> Of course before reading anything about Dogelog Player
> you have to start with the reference section also known
> as bibliography, which is found at the end of PDF here:
> 
> Dogelog Player Host Version 1.1.5, December 17, 2023
> https://www.novacuor.ch/doctab/rscsrv/docs/17_host/package.pdf
> 
> You need to first understand the below things before
> you dig and put your nose into Dogelog Player:
> 
> [1] ISO (1995): Prolog, Part 1: General Core,
> International Standard ISO/IEC 13211-1, First Edition, 1995-06-01
> http://www.iso.org/standard/21413.html
> 
> [2] Clocksin, W. (1983): A portable Prolog compiler, Logic Programming 
> Workshop, Albufeira Portugal, January 1983
> http://www.softwarepreservation.org/projects/prolog/lisbon/lpw83/p74-Bowen.pdf 
> 
> 
> [3] Carlson, M. et al. (1988): Garbage collection for Prolog based on 
> WAM. Communications of the ACM 31, 6, 719–740, June 1988
> http://dl.acm.org/doi/10.1145/62959.62968
> 
> Dogelog Player implements variants of [1], [2] and [3].
> SWI-Prolog also implementes [3], but it doesn't implement
> the generational part of [3]. Recently I managed to also
> 
> implement the generatioal part of [3] via some coloring
> approach. If I am not mistaken you find a blog about it
> also announced here and somewhere on medium.com.
> 
> And most recently I removed a cludge from change_arg/3
> also related to [3]. And according blog I also announced
> here to be exact 5 days ago. Its also on medium.com.
> 
> Maybe you need medium.com membership to be able to read it.
> 
> Mild Shock schrieb:
>> John Harris schrieb:
>>> Your JavaScript code includes some form of garbage collection. Has 
>>> that influenced the data structures ?
>>
>> There is a long thread about the early Garbage Collection
>> of Dogelog Player in comp.lang.python. Especially whether
>> it can be made fast, with useful input from a few
>> Pythonistas.
>>
>> Then I post regularly about the evolution of the GC
>> of Dogelog Player. It was just posted a few days ago,
>> when you were still on your silly tangent that my
>>
>> posts are nauseating. Now you are asking stuff, that
>> I am anyway posting about. Whats is wrong with you?
>> Do you have a PhD in being the most stupid person
>>
>> on this planet? See here, few days ago,
>> to be exact 5 days ago:
>>
>> Mild Shock schrieb 23.03.2024, 16:43:
>>  >
>>  > Dogelog Player is a Prolog system that features
>>  > a generational garbage collector scheme and a
>>  > change_arg/3 primitive built-in. So far the two
>>  > didn’t go together and we had to use a cludge.
>>  > With the upcoming release we provide a proper
>>  > solution based on marking write-barriers.
>>  >
>>  > Our remembered set on the variable binding trail
>>  > has the benefit that it can reduce itself during
>>  > backtracking. By adopting conductor variables, i.e.
>>  > instantiated variables that are not trailed, from
>>  > formerly Jekejeke Prolog, we could recreate a
>>  > similar benefit for Dogelog Players change_arg/3.
>>  >
>>  > See also:
>>  >
>>  > Marking Write-Barriers for Dogelog Player
>>  > https://twitter.com/dogelogch/status/1771559896741192186
>>  >
>>  > Marking Write-Barriers for Dogelog Player
>>  > https://www.facebook.com/groups/dogelog
> 

[toc] | [prev] | [next] | [standalone]

#124356

Starting with the Sudoku solver we have recently
obtained we developed a Puzzle generator together
with an interactive game play. The result can be
run in a web page by means of Dogelog Player 1.2.0
for JavaScript. Both the Puzzle generator and the
game play were written in 100% Prolog.

Regin Filtering from SWI-Prolog CLP(FD) didn’t
make a dent for generating unique puzzles, all we
could do was provide 34 clues, and our solver takes
in the average 1000 ms. We also implemented valid
move checking by reusing the constraints and an undo
move queue via dynamic facts.

See also:

Game Play of Spock Doku
https://twitter.com/dogelogch/status/1774936304335159561

Game Play of Spock Doku
https://www.facebook.com/groups/dogelog

Mild Shock schrieb:
> 
> Dogelog Player is a Prolog system that features
> a generational garbage collector scheme and a
> change_arg/3 primitive built-in. So far the two
> didn’t go together and we had to use a cludge.
> With the upcoming release we provide a proper
> solution based on marking write-barriers.
> 
> Our remembered set on the variable binding trail
> has the benefit that it can reduce itself during
> backtracking. By adopting conductor variables, i.e.
> instantiated variables that are not trailed, from
> formerly Jekejeke Prolog, we could recreate a
> similar benefit for Dogelog Players change_arg/3.
> 
> See also:
> 
> Marking Write-Barriers for Dogelog Player
> https://twitter.com/dogelogch/status/1771559896741192186
> 
> Marking Write-Barriers for Dogelog Player
> https://www.facebook.com/groups/dogelog

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | comp.lang.javascript

csiph-web