Jordi GutiƩrrez Hermoso | 12 Jul 2012 15:38
Gravatar

Imploding pkg.m

Can we please move the private functions of pkg.m back into pkg.m as
subfunctions? I don't find one-function-per-file to be easier to work
with than multiple functions per file. You don't do
one-function-per-file in any other language, do you?

- Jordi G. H.

Michael Goffioul | 12 Jul 2012 16:00
Picon

Re: Imploding pkg.m

On Thu, Jul 12, 2012 at 2:38 PM, Jordi Gutiérrez Hermoso <jordigh <at> octave.org> wrote:

Can we please move the private functions of pkg.m back into pkg.m as
subfunctions? I don't find one-function-per-file to be easier to work
with than multiple functions per file. You don't do
one-function-per-file in any other language, do you?

I'm wondering if there's also a performance penalty? (as instead of monitoring changes and reloading a single file, you have to do it for multiple files).

Michael.


Gmane