From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Thu, 14 Feb 2013 16:52:29 -0500
To: 9fans@9fans.net
Message-ID: <c0d703796a1f7efa7179e8b26a036533@ladd.quanstro.net>
In-Reply-To: <CAOw7k5jUoA4JvfXUCOvHufRGm_h-N+wD41jw4zS25pq_8inVNA@mail.gmail.com>
References: <d919cf445ee5bea75a3e5efa62d75d3a@ladd.quanstro.net>
	<CAOw7k5jb8V7MmUEXEu9Xcqh7Og7OUy-ycO_DDrwtN5zeqLsCPg@mail.gmail.com>
	<805566779b1b3d1c546d6ae020156ada@ladd.quanstro.net>
	<CAOw7k5jUoA4JvfXUCOvHufRGm_h-N+wD41jw4zS25pq_8inVNA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] why does this compile?
Topicbox-Message-UUID: 184f1cc8-ead8-11e9-9d60-3106f5b1d025

On Thu Feb 14 16:49:17 EST 2013, charles.forsyth@gmail.com wrote:

> No, but the value at least isn't bizarre. It would be correct for rloge as
> an array, and i assume it gets through because of the way the
> array->pointer change is done. Even so, if it had been GCC, by now it would
> be an essential extension, and have been used to implement an elisp
> interpreter, shave micro cycles from the time of a Java vm , and by GCC
> itself. I might look at nipping all that in the bud tomorrow, although I
> think I have looked at this once before.

thanks.

- erik