[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Octave
From: |
Sergei Steshenko |
Subject: |
Re: Octave |
Date: |
Sun, 13 Apr 2014 14:42:48 -0700 (PDT) |
----- Original Message -----
> From: Ben Abbott <address@hidden>
> To: c. <address@hidden>
> Cc: Sergei Steshenko <address@hidden>; eugenio.pariani <address@hidden>;
> "address@hidden" <address@hidden>
> Sent: Monday, April 14, 2014 12:36 AM
> Subject: Re: Octave
>
>
> On Apr 13, 2014, at 5:29 PM, c. <address@hidden> wrote:
>
>>
>> On 13 Apr 2014, at 23:09, Sergei Steshenko <address@hidden>
> wrote:
>>
>>> I don't know what it means from Octave developers point of view
> though.
>>
>> it means that the output is not assigned if nargout = 0.
>>
>>
>> It seems to me that the fix is trivial, as the documentation says
>> that only one output value is assigned in any case, it would probably
>> be sufficient to change line 719 of libinterp/corefcn/input.cc from
>>
>> retval = eval_string (input_buf, true, parse_status, nargout);
>>
>> to
>>
>> retval = eval_string (input_buf, true, parse_status);
>>
>> please add this suggestion to the report when reporting the bug.
>>
>> c.
>
> I opened a bug report.
>
> https://savannah.gnu.org/bugs/index.php?42111
>
> Ben
>
It's funny to read this thread - there is a reply to my statement, and the
reply only partially quotes my statement (which contains a workaround in a
sense), but my message isn't there yet.
The list moderator is asleep ?
--Sergei.
- Octave, eugenio.pariani, 2014/04/13