Re: More everything into the octave namespace

[John W. Eaton]

On August 16, 2016 9:19:13 AM EDT, "Carnë Draug" <address@hidden> wrote:
>On 15 August 2016 at 23:59, John W. Eaton <address@hidden> wrote:

>> I've been doing this incrementally because I want to change most
>names that
>> are of the form "octave_foo" to be "octave::foo" instead.  So it's
>not as
>> simple as just inserting "namespace octave {" at the top of every
>file and
>> "}" at the bottom.
>>
>
>But that only applies to classes that are octave_foo.

Yes.  The others are slightly easier to move, but I still want to try to 
provide typedefs or other means for backwards compatibility in most cases.  So 
it's not as simple as running sed on some source files.

>Rik mentioned feature freeze the day after my original email so this
>change won't go through to 4.4 anyway.  However, there's classes that
>are new for Octave 4.2, and others that have changed since 4.0.  These
>are the ones that could be moved right away.

OK, let's identify those classes and fix them now.

jwe