> the STDERR behavior was intentional
1) It just does not seem to be logical: warning messages still get written
to STDERR. Why? And what is the use of STDERR, in general? STDERR is in the
documentation, without telling anything about it.
2) The REPL behavior ought to be documented, otherwise new users would
naively think that error messages are sent to STDERR, as regular console
(REPL) output is available in STDOUT, and user input is seen in STDIN. So
what is so special about error messages sent to STDERR? (Btw. error
messages are not sent to STDOUT, either, they are just displayed in the
console window.)
> Steve Johnson has provided solutions several times
Unfortunately, his solutions either don't work or they are so complicated,
that I cannot include them into my programs.
> println("RESULT: ", eval(parse(readline())))
As we discussed it several times, this does not work with multi-line input.
Sure, I can write my own REPL, but this is not the issue here. We should
not have to do it, since there is one included in the Julia distribution.
It just does not seem to have sufficient documentation.
On Wednesday, July 16, 2014 8:07:00 PM UTC-6, Jameson wrote:
>
> I think the change in the STDERR behavior was intentional, once we got rid
> of the limitations of using libreadline. Now we can run multiple
> simultaneous independent REPL loops, thanks to Keno's work. Redirecting
> STDERR and having that propagate to the stderr stream used by the REPL was
> a limitation in 0.2 which no longer exists in 0.3. I wouldn't expect it to
> be reintroduced.
>
> Steve Johnson has provided solutions several times. Such as
> https://gist.github.com/stevengj/88502943fe0478933492, if you want to
> hook into the existing REPL, or
> while true
> println("RESULT: ", eval(parse(readline())))
> end
> if you want to roll your own.
>
> Implementing a good REPL requires interacting with the user, so it is
> inherently a hard task and thus may needs a fairly large amount of code to
> configure and manage the program's state to stay synchronize with the
> user's expectations.
>
> PS: https://github.com/JuliaLang/julia/issues/7633
>
>
> On Wed, Jul 16, 2014 at 8:48 PM, Laszlo Hars <[email protected]
> <javascript:>> wrote:
>
>> I don't know, how to file an issue. Where can I get instructions? (The
>> STDERR behavior may be intentional. I kept asking about it in this group,
>> for months, but nobody was interested.)
>>
>>
>> On Wednesday, July 16, 2014 6:36:23 PM UTC-6, Kevin Squire wrote:
>>
>>> Interesting. Can you (or did you) file an issue?
>>>
>>> Cheers,
>>> Kevin
>>>
>>>
>>> On Wed, Jul 16, 2014 at 4:36 PM, Laszlo Hars <[email protected]> wrote:
>>>
>>>> I hoped that at some point Julia error messages would again appear in
>>>> STDERR. No luck. Even the Release candidate 0.3.0-rc1 fails to write, e.g.
>>>> DomainError to STDERR (provoked by 1^-1 entered in the Windows REPL).
>>>> Maybe
>>>> the documentation should mention that STDERR is for warnings, only.
>>>>
>>>
>>>
>
