On 29/03/2013 20:24, Rob Arthan wrote:
Quite a common thing to do in UN*X applications is not to prompt if the input isn't a terminal. Obviously, I can write my own read-eval-print loop that does that (indeed the read-eval-print loop in my earlier post on this topic doesn't prompt at all), but it might be a nice companion to the change you have just made to make the top level do that out of the box. That would give Gergely Buday exactly what he is asking for (i.e., the ability to have poly read code from the standard input and only output what the compiled code outputs).
I guess it could suppress the prompt if the input was from a file but generally I wouldn't want to suppress it if it came from a pipe. On Windows I normally run Poly/ML within an environment that provides editing and communicates to the Poly process through pipes. Since it's interactive I want the normal prompts. It's difficult to see how to distinguish this from "cat file.ML | poly".
David _______________________________________________ polyml mailing list [email protected] http://lists.inf.ed.ac.uk/mailman/listinfo/polyml
