[m-users.] Support for vanilla prolog

[Stuart Reynolds]

Mercury presents a fork
For me the benefits of strong typing is faster development of prolog in
language that's painfully slow to write and debug.
OTOH, ISO prologs have a considerable number of useful libraries
(visualization, database connectors). Dynamism itself is also occasionally
often useful.
Optional typing would seem to make it straightforward to incorporate
dynamically typed prolog, but gain the benefits of strong typing for new
code.


On Thu, May 28, 2020 at 7:20 PM Julien Fischer <jfischer at opturion.com>
wrote:

>
> Hi Stuart,
>
> On Thu, 28 May 2020, Stuart Reynolds wrote:
>
> > I'm sold on the value of strong typing. However, it makes integration
> > with existing Prolog codebases problematic. It there support for
> > optional typing that would allow Mercury to be used more fluidly with
> > existing prolog?
>
> What do you mean by integrating with existing codebases?  Do you mean
> (1) converting that codebase to run in Mercury or (2) having some
> component written in Mercury communicate with Prolog?
>
> Julien.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurylang.org/archives/users/attachments/20200528/3e675ab6/attachment.html>