John Clements wrote:
On Oct 5, 2010, at 3:25 PM, Ryan Culpepper wrote:
I seem to have mangled my response right before sending it. Here it is again,
hopefully straightened out.
On 10/05/2010 03:59 PM, John Clements wrote:
A couple of weeks ago, you showed me the trick that rackunit uses to a
On Oct 5, 2010, at 3:25 PM, Ryan Culpepper wrote:
> I seem to have mangled my response right before sending it. Here it is again,
> hopefully straightened out.
>
> On 10/05/2010 03:59 PM, John Clements wrote:
>> A couple of weeks ago, you showed me the trick that rackunit uses to allow
>> sing
I seem to have mangled my response right before sending it. Here it is
again, hopefully straightened out.
On 10/05/2010 03:59 PM, John Clements wrote:
A couple of weeks ago, you showed me the trick that rackunit uses to allow
single-instantiation of a modules. I'm now trying to do this
for a
On 10/05/2010 03:59 PM, John Clements wrote:
A couple of weeks ago, you showed me the trick that rackunit uses to allow
single-instantiation of a modules. I'm now trying to do this
for a planet package, and it looks like I have to change the required module
from being a relative to being an ab
John,
See "this-package-in", found both in the cce/scheme planet package and
in unstable/require. If you write (prefix-in drlink: (this-package-in
private/drracket-link)) you should get the behavior you want, and it
should be less fragile than the explicit "planet" path.
Carl Eastlund
On Tue, O
A couple of weeks ago, you showed me the trick that rackunit uses to allow
single-instantiation of a modules. I'm now trying to do this
for a planet package, and it looks like I have to change the required module
from being a relative to being an absolute path. That is:
(require (prefix-in drl
6 matches
Mail list logo