hi tony---thanks. I will keep an eye on the docs (presumably streams).
from a novice end-user (not developer) perspective, solving the specific
snippet that I noted would be great in the documentation pages. regards,
/iaw
Ivo Welch (ivo.we...@gmail.com)
http://www.ivo-welch.info/
J. Fred
Ivo,
It looks like https://github.com/JuliaLang/julia/pull/12807 would implement
the suggestion to change open(command) to return just the process instead
of a tuple, so indexing into the return from open(`gzcat myzippedfile.gz`)
would no longer be necessary.
-Tony
On Saturday, February 27,
another strange definition from a novice perspective: close(x1) is
not defined. close(x1[1]) is.
close() is defined for a stream, not a tuple (stream, process).
julia is the first language I have
seen where a close(open(file)) is wrong.
FWIW, I believe that there was concern that the
hi kevin---I would be happy to open an issue, but I would prefer if
the honor was left to someone (you?) who can articulate it better.
I am a true novice here.
if I understand it right, the fix is easy. is a Handle change
complex and/or needed? just overload all functions that expect a Pipe
to
On Monday, January 5, 2015 9:09:41 AM UTC-5, Kevin Squire wrote:
FWIW, I believe that there was concern that the behavior of open(process)
might cause confusion when it was defined in this way. (A quick search
didn't locate the issue.)
See the discussion at
It seems perhaps that each Process instance should remember its IO streams,
so that it could be used directly as an IO object.
On Mon, Jan 5, 2015 at 2:32 PM Steven G. Johnson stevenj@gmail.com
wrote:
On Monday, January 5, 2015 9:09:41 AM UTC-5, Kevin Squire wrote:
FWIW, I believe that
dear julia users: beginner's question (apologies, more will be coming).
it's probably obvious.
I am storing files in compressed csv form. I want to use the built-in
julia readcsv() function. but I also need to pipe through a decompressor
first. so, I tried a variety of forms, like
d=
