On May 16, 2011, at 11:25 AM, Matthew Flatt wrote:
> At Mon, 16 May 2011 14:19:05 -0400, Stephen Chang wrote:
>>> This question is somewhat vague but I've been able to replicate it
>>> pretty reliably so I'll ask anyways. I'm running redex-check for a
>>> long time and after about 6-8 hours, drra
Yes, just changing the default.
"raco test -r" will behave like "racket -t" unless there is a test
submodule, in which case, it will actually run the tests.
Jay
On Fri, Mar 9, 2012 at 10:04 PM, Sam Tobin-Hochstadt wrote:
> On Fri, Mar 9, 2012 at 9:54 PM, Jay McCarthy wrote:
>>
>> I intend to c
On Fri, Mar 9, 2012 at 9:54 PM, Jay McCarthy wrote:
>
> I intend to change DrDr so that it always uses "raco test -r" rather
> than "racket -t".
I assume you mean just changing the defaults. Will this resulting in
running any less code?
--
sam th
sa...@ccs.neu.edu
_
R
I've renamed
module* to slice
and removed its ability to specify a language other than #f (maybe it
could be a #:keyword later)
I've removed when-testing because (slice test ...) is shorter than
(begin-for-testing test ...) [which, btw Carl, is the best name.]
I've expanded 'raco test' to suppo
30 minutes ago, Matthew Flatt wrote:
>
> How about `facet', with the terminology that "facets" are
> implemented as "submodules"?
I like using a different term with just that explanation (ie, "a facet
is a particular kind of a submodule").
But I still don't like `facet' -- not only because of my
I'll reply to the rest later, but two quick ones:
Just now, Matthew Flatt wrote:
> > How about just (submodule foo ...) be a more memorable syntax for
> > (module* foo #f ...)?
>
> That was Jon's suggestion, and my objection is that "submodule"
> means something more general than those nested mo
At Fri, 9 Mar 2012 15:58:11 -0700, Jay McCarthy wrote:
> I just pushed...
>
> - module**
>
> Like module* but combines multiple occurrences of the same submodule
> name into one module*
I like this direction --- and like everyone, I wish for a better name.
I don't like `submodule' or `sub' for
At Fri, 9 Mar 2012 16:35:25 -0500, Eli Barzilay wrote:
> Two days ago, Matthew Flatt wrote:
> >
> > Given the term "submodule", the first thing that you're likely to try
> > will work as expected:
> >
> > #lang racket/base
> >
> > (module zoo racket/base
> > (provide tiger)
> > (defi
Some more comments:
* There's probably a better way to collect the expression lists than
set!-ing it.
* `sub' is probably a bad name, though `submodule' looks too long for
this.
[
* I should have said earlier that if there's a `when-testing' then the
bad result is adding a `when-in-main'
A few minutes ago, Eli Barzilay wrote:
> [...] Here's what I have in mind:
(Other things were broken there...)
Here's the code that works now:
(sub tests (require tests/eli-tester)) ; make it known before main
(sub main (printf "Welcome to MY library!\n"))
(define (plus x y) (+ x y))
Just now, Jay McCarthy wrote:
> I just pushed...
>
> - module**
>
> Like module* but combines multiple occurrences of the same submodule
> name into one module*
But... it adds more stars... I don't think that there's any need for
a convenience macro that does just the combining, since that feat
On Fri, Mar 9, 2012 at 5:58 PM, Jay McCarthy wrote:
> I just pushed...
>
> - module**
>
> Like module* but combines multiple occurrences of the same submodule
> name into one module*
>
> - when-testing
>
> An abbreviation of module** with the name test and the #f language
>
> - raco test
>
> Find
I just pushed...
- module**
Like module* but combines multiple occurrences of the same submodule
name into one module*
- when-testing
An abbreviation of module** with the name test and the #f language
- raco test
Finds all the files in a directory and requires their test module
I like the na
On Mar 9, 2012, at 1:29 PM, Jay McCarthy wrote:
> Yes. I should definitely fix that, whether or not I implemented
> chunked transfers.
FWIW, chunked transfers *are* implemented on the receiving side; there are
tests in net/url/tests (sp?) that explicitly check the ability to reassemble
chunked
[Some of these points may have come up earlier, I just didn't want to
lose comments so reply as I read it.]
[To be clear in advance, the following should be qualified by an "I
love it".]
Two days ago, Matthew Flatt wrote:
>
> Given the term "submodule", the first thing that you're likely to try
Yes. I should definitely fix that, whether or not I implemented
chunked transfers.
Jay
On Fri, Mar 9, 2012 at 2:18 PM, John Clements wrote:
>
> On Mar 9, 2012, at 12:18 PM, Jay McCarthy wrote:
>
>> There is nothing going wrong with the supported features of the Web
>> server. It's just that the
On Mar 9, 2012, at 12:18 PM, Jay McCarthy wrote:
> There is nothing going wrong with the supported features of the Web
> server. It's just that the Web server doesn't support any
> Transfer-Encoding other than the default of no encoding.
From RFC2616:
"A server which receives an entity-body wit
There is nothing going wrong with the supported features of the Web
server. It's just that the Web server doesn't support any
Transfer-Encoding other than the default of no encoding.
Jay
On Fri, Mar 9, 2012 at 1:44 AM, John Clements wrote:
> My students are working on an assignment that has them
Does anyone mind avoiding compilation of `collects/tests/*'?
I'm counting now about 10% of the tree build time spent on compiling
stuff in collects/tests. Probably a large part of that is the eopl
tests, since most of the other big tests already disable compilation.
I could just add the info file
Hello,
I'm optimizing some code and have used gc-info logging
to correlate substantial application pauses with GC occurrences. This make
sense. The obvious solution is to allocate less memory, but tracking down
where it's coming from isn't easy. In the short term I plan to inject
(current-memor
30 minutes ago, Jay McCarthy wrote:
> I'll pushed an improved version of the test macro shortly.
Please don't put it in `racket/test', since it's not a testing thing.
(I haven't got to reply to that yet, but it looks like a more general
convenience macro for pulling some expressions into a submod
What about specially treating the #:main keyword when it appears in a
module top-level. Everything that follows it gets wrapped in a
(module* main #f), perhaps with #:niam as an end delimiter. Or maybe
#:submodule , if it appears at the top-level of a module could
mean that. Or maybe all new syntax
I'll pushed an improved version of the test macro shortly.
Jay
On Fri, Mar 9, 2012 at 11:04 AM, Matthew Flatt wrote:
> At Wed, 7 Mar 2012 10:14:35 -0700, Matthew Flatt wrote:
>> I've added "submodules" to a version of Racket labeled v5.2.900.1
>
> Submodules are now pushed to the Racket git repo
Two days ago, Matthew Flatt wrote:
>
> If you don't need this functionality enabled by default, you could
> install a `load/use-compiled' handler that similarly recognized
> paths into a ".zip" file.
The problem with that is that it's a hook that gets used only for
loading code -- a lower level h
At Wed, 7 Mar 2012 10:14:35 -0700, Matthew Flatt wrote:
> I've added "submodules" to a version of Racket labeled v5.2.900.1
Submodules are now pushed to the Racket git repo.
I haven't yet added a syntactic form to simplify
(module* main #f
)
My first idea was `main', as in
(main
.
Just in case: if you use gmail, make sure your encoding is set to UTF-8.
Thanks, Eli!
Robby
On Fri, Mar 9, 2012 at 2:46 AM, Eli Barzilay wrote:
> In preparation for a move to github, I've finished a very long and
> tedious[*] scan of the complete gnats db, and everything is now
> properly utf8-
Robby Findler wrote at 03/08/2012 08:00 PM:
I think that the issue probably does not predate Kevin's recent push
(distributed places).
If you'd like to audit the push security concerns, I'm sure that'd be welcome.
I meant that I might need to take a look at it because the example we
saw w
In preparation for a move to github, I've finished a very long and
tedious[*] scan of the complete gnats db, and everything is now
properly utf8-ized. In addition, the web interface declares a utf8
charset which means that the texts are fine there too. There is one
problem that is still left: inc
My students are working on an assignment that has them CPS and defunctionalize
a small evaluator so that they can ship computations from one compute server to
another:
http://www.brinckerhoff.org/clements/csc430-wi12/Assignments/ass7.html
As part of this assignment, some of the students are wri
29 matches
Mail list logo
