The next version of Savant is going to focus heavily on the stand-alone runtime anｄ support for dialects anｄ plugins. Supporting all that is largely handled by using a simple executor framework I wrote around Java 1.4 anｄ lower’s Runtime.exec method. A few things to keep in mind when using this:
Always read from the streams prior to calling waitFor. Otherwise you could end up waiting forever on Windows anｄ other OS platforms whose I/O buffers can’t store enough from standard out anｄ standard error to ensure the program has finished. These platforms will pause the execution of whatever is running until something reads the buffered content from standard out anｄ standard error. I would imagine all platforms suffer from this, but some platforms have larger buffers than others. Needless to say, always read from the streams first.
Always read from standard error first. I ran across a bug where some OS platforms will always open standard out, but never close it. What this means is that if you read from standard out first anｄ the process only writes to standard error, you’ll hang forever waiting to read. If you read from standard error first, you’ll always be okay on these platforms because the OS seems to shutdown standard error. I think however, that the best way to handle all cases is to check both standard error anｄ standard out for readiness anｄ only read from them if they have something to offer. The downside I could see here is that error isn’t ready, but eventually will be.
?????????? String []cmdArray = new String[]{ "/bin/sh", "-c", "yourscriptname"};
?這樣的調用方式，會為腳本執行創建出一個tty環境，否則，運行過程會提示"sorry, you must have a tty to run xxx"的錯誤。
Because some native platforms only provide limited buffer size for standard input and output streams, failure to promptly write the input stream or read the output stream of the subprocess may cause the subprocess to block, and even deadlock.
