[plt-scheme] Exposing non-exported module variable bindings.

From: Dor Kleiman (dor at ntr.co.il)
Date: Wed Dec 17 09:31:19 EST 2003

Open DrScheme; open the file that contains the module you would like to
test. Choose the language 'module'. Then, click Execute. The module that
you are testing will actually be the top run-level, and the REPL would
be able to use its unexposed variables.

-----Original Message-----
From: Richard C. Cobbe [mailto:cobbe at ccs.neu.edu] 
Sent: Wednesday, December 17, 2003 4:20 PM
To: Dor Kleiman
Cc: Matthew Flatt; Raymond Racine; plt-scheme at list.cs.brown.edu
Subject: RE: [plt-scheme] Exposing non-exported module variable

Lo, on Wednesday, December 17, Dor Kleiman did write:

> Why would you want to expose those variables anyway?

White-box testing.

> If for using them in code, it sounds quite wrong to do it.
> If for debugging, they are exposed anyway when using the module
> language...

I agree with the first; I'm not quite sure what you mean by the second.

This situation is just an instance of the general problem that one of
the costs associated with increased abstraction and firmly-enforced
abstraction boundaries is a lack of testability.


Posted on the users mailing list.