[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Carlo De Falco
Thu, 20 Aug 2015 10:14:10 +0000
On 19 Aug 2015, at 20:57, John W. Eaton <address@hidden> wrote:
> On 08/19/2015 09:54 AM, Carlo De Falco wrote:
>> In version 3.8 the method octave_value_base::print was declared as:
>> void octave_value::print ( std::ostream &os, bool pr_as_read_syntax = false)
>> while in 4.0 and 4.1 it is declared as:
>> void octave_base_value::print (std::ostream & os, bool pr_as_read_syntax =
>> what was the reason for removing "const"?
>> this has given me some compatibility trouble for some packages,
>> I can easily work around it, but I am curious why should the print method be
>> allowed to be non const?
> As I recall, it was needed for classdef.
OK, I suspected that, thanks.
> Here is the changeset:
> Would it make sense (and is it possible) to provide const and non-const
I think it is possible but I'm not sure whether it makes sense.
If you think it does I can prepare a changeset.