[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Namespacing and directories under libinterp/
From: |
Jordi Gutiérrez Hermoso |
Subject: |
Namespacing and directories under libinterp/ |
Date: |
Fri, 31 May 2013 14:26:12 -0400 |
On 31 May 2013 14:18, John W. Eaton <address@hidden> wrote:
> This reminds me of how we caved in to the pressure from some novice Octave
> developers and rearranged the Octave source tree last year. The novices
> thought the number of files in the liboctave and src directories was
> intimidating. And they assumed that it would be easier to see the structure
> of the sources if they were split up into more logical groups of functions.
> Since then, I've had nothing but trouble finding files. I don't think the
> extra directory levels in liboctave and libinterp really helped me at all,
> and they probably just make it more confusing for people -- WTF is the
> difference between libinterp/corefcn and libinterp/interp-core?
I think those are the only two where the distinction isn't clear. Or interpfcn.
But I actually like the liboctave breakdown. And I like octave-value
and the parse tree classes in their own respective directories; those
are already de-facto namespaced by having ov- or pt- in front of the
source files.
If we create a namespace for Octave, it should be just one, and no
nested namespaces. octave:: seems fine to me.
- Jordi G. H.
- Namespacing and directories under libinterp/,
Jordi Gutiérrez Hermoso <=