[racket] Problem around Creating Excutables

On Thu, Jan 2, 2014 at 4:09 PM, 亀田馬志 <masashi.kameda at gmail.com> wrote:

> Is this O.K? or do I have to put (flush-output) every time after (display)?

without flush-output what you write in the stream remains in a buffer
and is actually written out only when the buffer is full. You must use
flush-output when you want to be sure that what you wrote is actually
displayed on the screen, for example, before reading a string from the
user.

If you define your own print and read functions, as in the snippet
above, you can put the flush-output in them.

> The second question is... The game I compiled is, after shown several
> processes I made, got Abend, though running on Racket Interpreter is fine.
> What is the reason of this? Do I have to put something like
> (current-input-port)
>  stuff?

If you use no foreign code, probably this indicates that there's a bug
in Racket that only the developers can address. And they will need a
way to reproduce the crash, to look at it.

Cheers
P.