News for hackers. Stuff that matters.

A comment on How Lisp Became God's Own Programming Language. Parent comment

Re:How Lisp Became God's Own Programming Language by marcosdumay on Tuesday October 16, 2018 @12:41PM (#18230822)
I always have problems with the definition of homoiconicism...

Prolog code is represented the same way as data, but (AFAIK) there is no functionality for manipulating code at run-time or interpretation-time. I believe allowing macros is a necessary condition for homoiconicism, if I'm right, then Prolog isn't it.

[ Parent | on HN ]
Re:How Lisp Became God's Own Programming Language by carapace on Tuesday October 16, 2018 @03:08PM (#18232217)
> there is no functionality for manipulating code at run-time or interpretation-time

Sure there is: http://www.swi-prolog.org/pldoc/man?section=manipterm

Example:

    ?- foo(Bar, Baz) =.. List.
    List = [foo, Bar, Baz].
And:

    ?- F =.. [foo, Bar, Baz].
    F = foo(Bar, Baz).
[ Parent | on HN ]
Re:How Lisp Became God's Own Programming Language by 3rdAccount on Tuesday October 16, 2018 @01:11PM (#18231123)
No, I think just code is data is code right?

Also, I'm not sure macros are needed for a language which doesn't do compilation.

[ Parent | on HN ]
Re:How Lisp Became God's Own Programming Language by cjallen88 on Thursday October 18, 2018 @02:51PM (#18251053)
You can do all that with term-rewriting in Prolog, you can use a grammar to parse a file of arbitrary text and transform it into prolog terms to be executed etc
[ Parent | on HN ]