[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #49632] evalc() not capturing output from glpk
From: |
Mike Miller |
Subject: |
[Octave-bug-tracker] [bug #49632] evalc() not capturing output from glpk() |
Date: |
Sat, 17 Dec 2016 20:35:36 -0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0 |
Update of bug #49632 (project octave):
Severity: 3 - Normal => 1 - Wish
Item Group: Incorrect Result => Feature Request
Status: None => Confirmed
Release: 4.2.0 => dev
_______________________________________________________
Follow-up Comment #1:
Confirmed, this is because the glpk library writes to the stdout stream
directly, which Octave is not currently attempting to capture completely.
Octave only captures the output that its functions produce, which is the same
as would be captured by the "more" and "diary" functions.
The same occurs if I write a compiled oct file that writes to stdout directly,
or run a subprocess that writes to stdout:
>> evalc ("system('ls -l')");
## output of ls is displayed on the terminal anyway
>> saysomething ## saysomething calls printf to stdout
hello
>> evalc ("saysomething");
hello
## output is still printed on the terminal and not captured
Retagging this as an enhancement that someone might want to work on. I have no
idea whether Matlab's evalc captures everything sent to stdout, including
library code and subprocesses, or only output from Matlab itself.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?49632>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Octave-bug-tracker] [bug #49632] evalc() not capturing output from glpk(),
Mike Miller <=