When `raco setup' builds documentation, it now puts cross-reference
keys and dependency information into an SQLite database. So, building
documentation now requires that SQLite is installed (on Unixes; SQLite
is installed by default on Mac OS X, and Racket includes SQLite on
Windows).
The changes
Rho! Cute!
I just realized that implicit quasiquoting won't work, for exactly the
same reason not quasiquoting doesn't work: (array ((1 2))) is still
ambiguous. If "(" always meant "row" then "," could be an escape, but
(array (,'(1 2))) is also hideous, and so is (array ,'(1 2)).
I'm starti
Oh, I see. I guess the best thing is to use the vector notation, but
insist that things are not quoted and the #() notation is used only to
say where the rows are (with expressions inside). You could also use a
one-letter identifier at the start of each parenthesized row:
(array [ρ [ρ [ρ "00" "0
Without extra assumptions, it's impossible to tell what's supposed to be
an element and what's supposed to be a row. For example, this is ambiguous:
(array ((list 1 2)))
It could be a one-dimensional array containing just '(1 2), or a 1x3
array containing 'list, '1 and '2.
My current "extr
Okay, I can't resist: why not use parens?
On Fri, Nov 23, 2012 at 4:31 PM, Neil Toronto wrote:
> On 11/23/2012 03:03 PM, Robby Findler wrote:
>>
>> That [implicitly quasiquoting array data] sounds crazy, man. How about
>> #:keywords instead?
>
>
> Like this?
>
> (array #:keywords (list) ((list
On 11/23/2012 03:03 PM, Robby Findler wrote:
That [implicitly quasiquoting array data] sounds crazy, man. How about
#:keywords instead?
Like this?
(array #:keywords (list) ((list 1 2)))
Deciding how to print elements would be a problem.
If not, then I
think you're better off just going w
That sounds crazy, man. How about #:keywords instead? If not, then I
think you're better off just going with identifiers.
Robby
On Fri, Nov 23, 2012 at 3:39 PM, Neil Toronto wrote:
> On 11/23/2012 01:47 PM, Neil Toronto wrote:
>>
>> On 11/22/2012 11:33 AM, Eli Barzilay wrote:
>>>
>>> Two days ag
On 11/23/2012 01:47 PM, Neil Toronto wrote:
On 11/22/2012 11:33 AM, Eli Barzilay wrote:
Two days ago, Neil Toronto wrote:
Anyway, it occurred to me that I need to provide a more robust way
to generate code for literal arrays anyway. Keywords are more easily
preserved by macros than syntax prope
On 11/22/2012 11:33 AM, Eli Barzilay wrote:
Two days ago, Neil Toronto wrote:
Anyway, it occurred to me that I need to provide a more robust way
to generate code for literal arrays anyway. Keywords are more easily
preserved by macros than syntax properties:
Why not use vector syntax #(...) ins
I don't think there is a source-level representation that has those
operations explicit in Racket. If you need to change the way closures
are represented to do your experiments, you will probably have to work
at a very low-level.
I think it would help you to look at Casey's model of the Racket
mac
I mean the difference between a constant closure that takes an extra vector
argument for the environment and a Racket closure that has its own environment
representation.
Lightweight closure conversion and super-beta inlining both need a way to
access surrounding environments for the shared bind
Sorry --- I don't understand what you mean by "lightweight closures use
the same representation".
If you convert a `lambda' so that it doesn't capture any variables ---
perhaps because you moved formerly captured variables to a vector
argument --- then the compiler will compile it as a constant cl
On Fri, Nov 23, 2012 at 1:20 AM, Nadeem Abdul Hamid wrote:
> 1. Do you use the automatic parentheses feature of DrRacket?
No.
> 3. If your answer to #1 is "No", why not? (Is it because you find its
> current behavior awkward in some way?)
Yes. Typing close parentheses is much less hassle than
8 hours ago, Nadeem Abdul Hamid wrote:
> The idea is to have DrRacket automatically skip over
> automatically-inserted closing parens if the user types one while
> the cursor is right in front of one. (The Eclipse Java IDE does this
> with various types of braces and parens, and in the past I've fo
14 matches
Mail list logo
