Well, first of all, there are these things called threads, guys, instead of spawning heavy weight processes. Just a thought ... Ta ta Take care, Sina -----Original Message----- From: brailleblaster-bounce@xxxxxxxxxxxxx [mailto:brailleblaster-bounce@xxxxxxxxxxxxx] On Behalf Of Susan Jolly Sent: Thursday, December 16, 2010 12:21 AM To: brailleblaster@xxxxxxxxxxxxx Subject: [brailleblaster] Re: Transforming C into Java In the first place, I don't see how you can avoid spawning some separate processes such as for printing and embossing. So you can't avoid that issue. As for rewriting your translator in Java, I can see advantages. However, I'm not familiar with any automated way of transforming C source to Java although Google suggests such tools might exist. My guess is that even if you could get something that worked, the resultant code would likely be unreadable and unmaintainable and with none of the advantages of human-designed Java code. Think how much trouble it is to convert print to braille, which is a much simpler problem. Susan