Re: evalc

[Rik]

On 03/28/2013 04:41 AM, address@hidden wrote:
> Message: 5
> Date: Thu, 28 Mar 2013 09:26:15 +0100
> From: Julien Bect <address@hidden>
> To: address@hidden
> Subject: Re: evalc
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 27/03/2013 15:02, Julien Bect wrote:
>> > On 25/03/2013 16:57, Rik wrote:
>>> >> Matlab describes evalc as
>>> >>
>>> >> "T = evalc(S) is the same as eval(S) except that anything that would
>>> >> normally be written to the command window, except for error messages, is
>>> >> captured and returned in the character array T (lines in T are 
>>> >> separated by
>>> >> \n characters). "
>>> >>
>>> >> So I think an m-file could be written that wraps around eval and
>>> >> temporarily redirects stdout to a file which could then be read into 
>>> >> [T].
>> >
>> > How would you do that in an m-file ? Using PAGER() ?
>> >
>> > How about hacking octave_pager_stream directly (changing its rdbuf) ? 
> I have almost have a working implementation of evalc() now, following 
> the second approach (hacking octave_pager_stream).
>
> Since evalc() is an unimplemented Matlab function, I assume that this 
> should be filed using a bug report ?
3/28/13

Julien,

Actually, if you have a patch that will implement it you should attach it
to the patch tracker which is a separate list on the Octave savannah
website (https://savannah.gnu.org/patch/?group=octave).

--Rik