On Sat, 17 Jan 2015 20:20:06 +0000 Graham Holden <sql...@aldurslair.com> wrote:
> > I'm skeptical of the notion that cmd.exe is diddling with your data > > I would echo this: it's good at mangling the command-line, but I've > not been aware of it ever mangling data sent to a file/stream (other > than the binary/text mode conversions). cmd.exe holds the camel-straw that convinced me to give up on Windows as a development platform. Say you're a Perl programmer and associate .PL files with perl.exe so that you can put .pl files on your PATH. (The documentation for assoc and ftype specifically mentions Perl as an example.) When launched though file-extension association, cmd.exe starts the process with all files closed (instead of three open). There is absolutely nothing you can do about it. Of course I'm not the first or only one to realize this, nor the only one inconvenienced. Of course the documentation doesn't mention that if invoked in this way your program ceases to be a filter, functionality every Perl programmer understands (and most expect). And of course the problem has remained unaddressed for decades. Thanks for listening. --jkl _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
