Andrew, The missing argument bug reproduced for me just fine. While I haven't tried reproducing the spurious junk behavior, I did go looking for a smoking gun, and sure enough, I think I found one, along with one more bug that you hadn't hit.
I committed a change to fxposix.ri to CVS; if you don't build from CVS let me know and I can send you a copy. Your report is prized, and if the change still doesn't fix it, let me know and I will look at it harder. This kind of thing gets shaken out by folks who properly test their work, but system(L) clearly hadn't been tested on Windows. The posix test suite entry that would have caught it is unfortunately, a UNIX-only test, so someone at some point needs to modify our current tests/posix suite to run reasonably also under Windows. Perhaps $ifdef's are acceptable under the circumstances. Cheers, Clint On Tue, Jun 9, 2009 at 12:01 AM, Andrew Clarke<acla...@civica.com.au> wrote: > You may remember I mentioned that system() seems to be losing the last > argument from the list. That's confirmed for the first call to system(). > > The next problem I've just noticed (on Windows) is spurious junk ending up > on the command line of the called process. However not the first call; the > 2nd, 3rd etc call to system progressively passes junk across. ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Unicon-group mailing list Unicon-group@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unicon-group
