[racket-dev] Can't use (current-output-port) with subprocess in DrRacket: does it matter?

I don't think it is possible with our current port support to make a
port that goes into a text% and returns #t to that predicate (is it?).

Robby

On Fri, Jan 7, 2011 at 2:36 PM, John Clements <clements at brinckerhoff.org> wrote:
> Currently, you can't run the mongodb tests in DrRacket, because they use "subprocess" with (current-output-port), which (in DrRacket) is not a file-stream port.
>
> In DrRacket's interactions window:
>
>> (file-stream-port? (current-output-port))
> #f
>
> Is this expected, or should DrRacket's current-output-port be a file-stream?
>
> John
>
>
> _________________________________________________
>  For list-related administrative tasks:
>  http://lists.racket-lang.org/listinfo/dev
>