>>17
It's in the Lisp family of languages, it shares many features with what was LISP around its time, but while functions and scope were changed(among other things), it retained Lisp's syntax as well a lot of its semantics. Scheme never officially supported low-level macros or reader macros as well as some other features present in more "real lisps", though you could get these features non-portably across implementations. Arc is rather simple, but it retains many base "Lisp" features, so its also a Lisp. newLISP is a new LISP, but its design is very antiquated(always dynamic scope and FEXPRs, as fully interpreted - have we not learned anything in the past 50 years?) - to its core it's still derived from other Lisps, so it is a Lisp, even if they could have chose better features to put in it. Dylan - this is a tough one, it heavily borrows a lot of Lisp semantics, but one very important core requirement to Lisps is "code=data" which it cannot retain if you're not using a homoiconic syntax, so it's hard to call it a Lisp, but given the close semantics(more close than some other "LISP"'s) you could call it a Honorary Lisp, even though there is no proper "code=data".