Re: Calling a function with undefined symbol

[Emanuel Berg]

Michael Heerdegen wrote:

> The exercise's goal was to recognize that `'x` evals to
> a symbol, which is something entirely different than adding
> another quote to that strange `'''....` value (which is not
> a symbol in any case). If you have understood that the first
> value is a symbol, it's easy to give the intended answers:
> two times "no".

Yes, but why do you need the "strange value" for that?

(setq one 1)

(eq    'one one) ; nil
(equal 'one one) ; nil

?

-- 
underground experts united
https://dataswamp.org/~incal