Those two seem like they can combine in strange ways.
Robby
On Mon, Nov 28, 2011 at 9:08 PM, Matthias Felleisen
wrote:
>
> I can see adding both disable-tests-above and disable-tests-below.
>
>
> On Nov 28, 2011, at 3:44 PM, Vincent St-Amour wrote:
>
>> At Mon, 28 Nov 2011 11:54:06 -0500,
>> Mat
I can see adding both disable-tests-above and disable-tests-below.
On Nov 28, 2011, at 3:44 PM, Vincent St-Amour wrote:
> At Mon, 28 Nov 2011 11:54:06 -0500,
> Matthias Felleisen wrote:
>> I propose
>>
>> 1. to remove the menu and its functionality
>> 2. to add a macro disable-tests-below
On Nov 28, 2011, at 09:07 , Geoffrey S. Knauth wrote:
> I did a git pull and rebuild of DrRacket this morning. All went well until
> make install hung at:
> raco setup: 1 running: xrepl/xrepl.scrbl
After a complete reboot, checkout from scratch and rebuild, all is well now.
__
At Mon, 28 Nov 2011 11:54:06 -0500,
Matthias Felleisen wrote:
> I propose
>
> 1. to remove the menu and its functionality
> 2. to add a macro disable-tests-below
> 3. and be prepared to add a macro enable-tests-below.
`disable-tests-below' makes it easy to accidentally skip running tests
alto
Robby Findler writes:
> On Mon, Nov 28, 2011 at 1:30 AM, Michael Sperber
> wrote:
>> Some tests (especially check-property-based tests) are expensive, and
>> you don't always want to run them - especially with world/universe-based
>> code. Is there a way to have that option only with the stude
On Nov 28, 2011, at 8:39 AM, Kathy Gray wrote:
> I don't recall our original reasoning, but I envision that with such a macro
> students will think they are only disabling the tests "below" the "call" and
> become confused. This isn't to say we shouldn't switch to a macro
I propose
1. to re
> It would be a whole lot nicer to insert> (disable-tests)> and>
> (enable-tests)> in the code, or perhaps to wrap a bunch of lines of code in>
> (with-tests-disabled ...)> or> (with-tests-enabled ...)
The Tracer does essentially this in reverse: by default you use the
Tracer language and "nothi
On Nov 28, 2011, at 8:39 AM, Kathy Gray wrote:
> I don't recall our original reasoning, but I envision that with such a macro
> students will think they are only disabling the tests "below" the "call" and
> become confused.
I can see why they might expect that. I can also see why they (or I)
On Nov 28, 2011, at 09:07 , Geoffrey S. Knauth wrote:
> I did a git pull and rebuild of DrRacket this morning. All went well until
> make install hung at:
> raco setup: 1 running: xrepl/xrepl.scrbl
In case this helps:
raco setup: 1 running: xrepl/xrepl.scrbl C-c C-c user break
user break
==
On Mon, Nov 28, 2011 at 1:30 AM, Michael Sperber
wrote:
> Some tests (especially check-property-based tests) are expensive, and
> you don't always want to run them - especially with world/universe-based
> code. Is there a way to have that option only with the student
> languages?
The option curr
I did a git pull and rebuild of DrRacket this morning. All went well until
make install hung at:
raco setup: 1 running: xrepl/xrepl.scrbl
CPU is pegged at 100%. This happened once before, and I rebooted, because the
WindowServer also jammed itself at 100% rendering the MBP (Lion) mostly
unre
I don't recall our original reasoning, but I envision that with such a
macro students will think they are only disabling the tests "below"
the "call" and become confused. This isn't to say we shouldn't switch
to a macro
-Kathy
On 28 Nov 2011, at 13:23, Matthias Felleisen
wrote:
Why
Why does this have to be a menu?
Why not add a macro to the test-engine code so that students can write
(disable-tests)
On Nov 28, 2011, at 2:30 AM, Michael Sperber wrote:
>
> Robby Findler writes:
>
>> [ moved to dev ]
>>
>> Apparently this broke somewhere in between v5.0 (June 2010)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Neil,
On 25-11-11 14:47, Neil Van Dyke wrote:
> As an immediate solution, I suggest simply not trying to use R6RS
> compatibility libraries with Racket, and instead just use the
> Racket language. Spend your energy on your application. (I don't
Sorry for the confusion. Ideally most of the syntax described will
beavailable in both pregexp and regexp mode, but "\\X" and
"\\u{E0}"should probably be restricted to pregexp only.
> To add to my confusion, your original email mentioned #px"n", which>
> currently matches a backslash followed
15 matches
Mail list logo
