BeanShell problem

Submitted by blind on Wed, 02/25/2004 - 18:56.

Hi,
When bsh is started in interactive mode (simply "bsh"), it doesn't respond to anything (well except Ctrl-C).
Marc (Denty) has already raised this issue on the mailing list, but I have seen no replies yet. It would be quite helpful to get it going, so anybody any idea?
Andras

‹ BeanShell

TFTP also effected

Submitted by markhale on Fri, 02/27/2004 - 14:04.

I have also noticed this problem with the TFTP client in interactive mode. I suspect the shell/console is consuming System.in rather than releasing it to the application, or something along those lines.

Sistem.in

Submitted by lsantha on Fri, 02/27/2004 - 21:52.

I have looked at this problem and I think we face a general problem with System.in . If you wrap System.in in a DataInputStream the deprecated readLine() methode works. If you wrap it in an InputStreamReader and a BufferedReader the readLine of the BufferedReader doesn't work. This might be due to a bug in the two later classes in GNU Classpath.
When trying with DataInputStream there is no echo in the console (you don't see what you type) but the data gets read in with readLine as it should. I modified the tftp client to use DataInputStream until this is fixed.
This might be a starting point for solving the problem.

BeanShell problem

Submitted by samreid on Fri, 02/27/2004 - 08:11.

I originally added the beanshell project to jnode, and my debug strategy (for the problem with interactive mode) was to spackle the original beanshell code with print statements, to try to track down the source of the problem. I had it isolated to within a couple of beanshell methods, but I couldn't see a solution. I think there is a discrepancy between what beanshell requires and what jnode provides.