by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Aug 10 15:01

    pmoura on master

    Additional tests for the `curre… Regenerate Handbook and API doc… (compare)

  • Aug 09 21:21

    pmoura on master

    Improve tests for the `bagof/3`… (compare)

  • Aug 07 07:45

    pmoura on master

    Fix duplicated test for the `at… (compare)

  • Aug 05 16:29

    pmoura on master

    Delete no longer used read-only… (compare)

  • Aug 03 20:16

    pmoura on master

    Improve tests for the `catch/3`… (compare)

  • Aug 03 18:39

    pmoura on master

    Improve tests for the cut contr… (compare)

  • Aug 03 08:42

    pmoura on master

    Additional tests for the `write… (compare)

  • Jul 31 17:53

    pmoura on master

    Fix some tests for the `atomic/… (compare)

  • Jul 31 11:25

    pmoura on master

    Add `uninstantiation_error/1` e… (compare)

  • Jul 31 10:09

    pmoura on master

    Fix test for the `keysort/2` Pr… (compare)

  • Jul 30 10:29

    pmoura on master

    Additional tests for Prolog sta… (compare)

  • Jul 30 10:12

    pmoura on master

    Additional tests for Prolog sta… (compare)

  • Jul 29 19:44

    pmoura on master

    Additional tests for the `(=..)… (compare)

  • Jul 29 06:50

    pmoura on master

    Add fonts used by Sphinx render… (compare)

  • Jul 29 06:18

    pmoura on master

    Update version to 3.41.0-b01 in… (compare)

  • Jul 29 05:25

    pmoura on lgt3400stable

    (compare)

  • Jul 29 03:51

    pmoura on master

    Change version to 3.40.0 stable… (compare)

  • Jul 28 14:29

    pmoura on master

    Minor fix to identifiers of the… (compare)

  • Jul 25 07:54

    pmoura on master

    Minor documentation fixes (compare)

  • Jul 24 14:22

    pmoura on master

    Add tests for the de facto stan… (compare)

LamentConfiguration
@LamentConfiguration
tyvm
LamentConfiguration
@LamentConfiguration
would that work for using the pack for swi?
Paulo Moura
@pmoura
No. Those instructions are for the Logtalk Windows installer. Didn't notice that you're talking about the Logtalk pack for SWI-Prolog.
For SWI-Prolog packs installation directory, see the SWI-Prolog documentation.
Note that the Logtalk pack is a deployment solution and thus not advised for development.
LamentConfiguration
@LamentConfiguration
I understand that my use case is strange at best lol, I just don't recall the last version of the pack wanting to install stuff on the c: drive even though the swi executable in question is on my f: drive.
Paulo Moura
@pmoura
That's most likely due to recent changes on pack handling by SWI-Prolog that affect all packs.
LamentConfiguration
@LamentConfiguration
gotcha, i hadn't noticed that, i'll poke around in that area and see what i can figure out (: ty again for all the help.
Paulo Moura
@pmoura
In any case, you can always use the Logtalk Windows installer instead of the pack. It's also a better solution with improved usability.
Anton Danilov
@Stranger2015
Hi Paulo
Anton Danilov
@Stranger2015
Could you tell me if this is a valid term expansion use case:
term_expansion(X, []).?
Paulo Moura
@pmoura
Hi. Yes, you can use term_expansion/2 to supress a term by expanding it to the empty list.
Anton Danilov
@Stranger2015
HI Paulo.
I have an idea about Logtalk:
Anton Danilov
@Stranger2015
Logtalk ->your own Prolog(-like) language as the single backend Prolog for Logtalk->backend Prologs.
What do you think?
YungTse Technology
@YungTseTech_twitter
@Stranger2015 The ability to sit atop backend Prologs is, to my mind, simultaneously the strength AND the weakness of Logtalk. Which is kind of an uncomfortable place to sit.
Anton Danilov
@Stranger2015
I agree . that's why I'm trying to implement standalone version of Logtalk. Above suggestion is just an idea to divide work with backend prologs in two parts.
The first one is the static the second is simplified (hopefully) version of existing task of transpiling logtalk to prolog.
Paulo Moura
@pmoura
@Stranger2015 The compilation of Logtalk code is the responsability of the Logtalk compiler, not of the backends, whose responsability is simply to run the compiler/runtime and the generated code. Logtalk is designed to extend, not replace Prolog. Thus, to work with any Prolog backend that provides suitable standards support. The only point for Logtalk to have its own Prolog backend would be to replace Prolog instead of extending it.
Anton Danilov
@Stranger2015
Having of Logtalk its own backend Prolog is IMHO simplyfing supporting of backend Prologs. Maybe I have insuffiucient knowledge of Logtalk, so I just afraid that the compilation to many targets (backends) intermix compilation +adoptation+support.
Paulo Moura
@pmoura
Supporting backends is about writing/maintaining the adapter files (whose contents are minimal for most systems) and testing (which is hard given the number of backends * number of operating systems). I don't see how writing a Logtalk own backend would help here.
Note that the Logtalk compiler generates intermediate Prolog code that is essentially portable.
Anton Danilov
@Stranger2015
Ok for example your own backend could support term expansion so you can use them in Logtalk to implement the transpiler.
Paulo Moura
@pmoura
No need.
The term-expansion mechanism is not a good solution to implement Logtalk. It's simply too limited.
E.g. the Logtalk linter takes advantage of internal compilation data to check for a large number of issues. Collecting, handling, and using that data using the term-expansion mechanism would be non-trivial and cumbersome.
Anton Danilov
@Stranger2015
btw what do you mean when you talk about EXTENDING Prolog?
I deem that extend means that Logtalk can do all that Prolog does + something that Prolog doesn't. =)
Paulo Moura
@pmoura
That's basically it.
Logtalk and Logtalk developer tools can solve problems that you cannot solve in a sensible way, if at all, using Prolog alone.
YungTse Technology
@YungTseTech_twitter
Be fair, Paulo: If Logtalk compiles to Prolog, it is self-evident you CAN solve it using Prolog alone. you just REALLY don't want to! :D
Paulo Moura
@pmoura
You can certanily do the work of the Logtalk compiler and tools by using hand written Prolog code. Good luck with that 😄
Anton Danilov
@Stranger2015
As one my fellow said:
Competent people write in assembler.
Paulo Moura
@pmoura
Assembler?!? Processor micro-code! 😄
Anton Danilov
@Stranger2015
Yeah! =)
Paul Bone
@PaulBone
But I don't write programs. I write programs that write programs.
Paulo Moura
@pmoura
Next: programs that write themselves! 😛
Paul Bone
@PaulBone
My favourite where the old graphics bliting code that would figure out the operations they needed to do, then write machine code for a tight loop to do it, and execute it.
Paulo Moura
@pmoura
SkyNet gran gran gran gran father?
Paul Bone
@PaulBone
:-)
Paul Brown
@PaulBrownMagic
There's a popular tweet/meme going round at the moment. In order for AI to write programs clients would have to accurately specify what they want, therefore our industry is safe. Made me chuckle.
Paulo Moura
@pmoura
😂😂😂
YungTse Technology
@YungTseTech_twitter
@Stranger2015 : Competent people write in the language that best suits the abstraction level they're working with.
Me, I use VHDL for everything.
:D
Anton Danilov
@Stranger2015
@YungTseTech_twitter
I agree, but that full quote:
LET NIKLAUS WIRTH WRITES IN HIS PASCAL BUT
COMPETENT PEOPLE WRITE IN ASSEMBLER
YungTse Technology
@YungTseTech_twitter
Assembler is OK, I guess, if you're a panty-waisted guy who doesn't like getting his hands dirty in the guts of the machine. :-/
Anton Danilov
@Stranger2015
I'm a lazy guy but I spend so much effort to afford myself to be lazy :D
YungTse Technology
@YungTseTech_twitter
My favourite lazy guy is Terence Parr, the man behind the PCCTS/Antlr suite of compiler compilers.
He spent a summer as an intern hand-coding a parser and hated it so much he spent the next 20 years of his life automating that process. :D
Anton Danilov
@Stranger2015
))))