Prolog and Lisp in .NET?
-
I read a thread about 100 languages, and one thing I don't understand. Common Language specs are quite strict regarding types that must be supported by .NET language. But some non-procedural languages don't have conventional types and methods. Take Prolog, for example - it's just predicates and atoms. You may of course "fake" the things in Prolog, like Borland did with Turbo Prolog - but then it was not the real thing. So when I'm reading about 100 languages, I ask myself: how different can they be? Just curious. Win32/ATL/MFC Developer Oslo, Norway
-
I read a thread about 100 languages, and one thing I don't understand. Common Language specs are quite strict regarding types that must be supported by .NET language. But some non-procedural languages don't have conventional types and methods. Take Prolog, for example - it's just predicates and atoms. You may of course "fake" the things in Prolog, like Borland did with Turbo Prolog - but then it was not the real thing. So when I'm reading about 100 languages, I ask myself: how different can they be? Just curious. Win32/ATL/MFC Developer Oslo, Norway
There will be versions of Mercury, ML, and Mondrian for .NET, all of which appear to be functional languages. How the interop with .NET is something I don't know about...
-
I read a thread about 100 languages, and one thing I don't understand. Common Language specs are quite strict regarding types that must be supported by .NET language. But some non-procedural languages don't have conventional types and methods. Take Prolog, for example - it's just predicates and atoms. You may of course "fake" the things in Prolog, like Borland did with Turbo Prolog - but then it was not the real thing. So when I'm reading about 100 languages, I ask myself: how different can they be? Just curious. Win32/ATL/MFC Developer Oslo, Norway
The .NET framework comes with sample implementation of a LISP compiler. If you have .NET istalled, it is zipped in c:\program files\microsoft.net\frameworksdk\tool developer guide\samples\samples.exe just extract it, and you will find a folder called \clisp Chaim J Nussbaum, MCP
-
The .NET framework comes with sample implementation of a LISP compiler. If you have .NET istalled, it is zipped in c:\program files\microsoft.net\frameworksdk\tool developer guide\samples\samples.exe just extract it, and you will find a folder called \clisp Chaim J Nussbaum, MCP
Thanks, I'll try it! Win32/ATL/MFC Developer Oslo, Norway