On Dec 8, 12:05 pm, Aaron Cohen wrote:
> On Wed, Dec 8, 2010 at 2:40 PM, javajosh wrote:
> > I was looking at quote.
>
> > user=> (quote 1)
> > 1
> > user=> (quote)
> > nil
> > user=> (quote quote)
> > quote
> > user=> ((quote quote) 1)
> > nil
>
> > It's the last result that confuses me. I would
On 12/8/2010 4:26 PM, Meikel Brandmeyer wrote:
Hi,
Am 08.12.2010 um 22:06 schrieb Tim Daly:
There are 2 kinds of lisps based on the meaning of a symbol.
Symbols have structure "slots".
And then there is clojure where symbols are just symbols without any slots. When the
compiler encounters
Hi,
Am 08.12.2010 um 22:06 schrieb Tim Daly:
> There are 2 kinds of lisps based on the meaning of a symbol.
>
> Symbols have structure "slots".
And then there is clojure where symbols are just symbols without any slots.
When the compiler encounters a symbol it resolves it to a Var or let local
There are 2 kinds of lisps based on the meaning of a symbol.
Symbols have structure "slots".
The first kind of lisp has symbols with a "function slot"
and a "value slot". The second kind of lisp has only the
"value slot". This affects the meaning of a symbol when
it is used in the first positio
On Wed, Dec 8, 2010 at 2:40 PM, javajosh wrote:
> I was looking at quote.
>
> user=> (quote 1)
> 1
> user=> (quote)
> nil
> user=> (quote quote)
> quote
> user=> ((quote quote) 1)
> nil
>
> It's the last result that confuses me. I would have expected the
> result to be "1" - e.g. the same as (quot
I was looking at quote.
user=> (quote 1)
1
user=> (quote)
nil
user=> (quote quote)
quote
user=> ((quote quote) 1)
nil
It's the last result that confuses me. I would have expected the
result to be "1" - e.g. the same as (quote 1). I figured I'd try quote
on something other than itself, and it just
