octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bioinfo package - maintenance of ...


From: Michael D Godfrey
Subject: Re: bioinfo package - maintenance of ...
Date: Tue, 19 Dec 2017 13:13:49 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0



On 12/19/2017 07:41 AM, Julien Bect wrote:
Le 19/12/2017 à 06:10, Oliver Heimlich a écrit :
(On a side note: interval is not Matlab compatible

My mistake.  I thought it was.  But symbolic is, isn't it ?


The reason why Octave coding style is requested for packages is twofold: (a) it shall allow to easily move a function from a package into Octave core or into another package, (b) it shall be easier to contribute to community maintained packages for all of us, which is easier when all packages follow a corporate style.
Reason (a) is probably irrelevant for several packages. If only small functions are of interest, the effort would be small to convert them into Octave style.

Reason (b) is really important because I'd like to see more contributions to packages happening and a common style helps with that in the long run. It simplifies to accept contributions if you don't have to reformat the patches.

Sure, I would also like to see more contributions happening ;-)

And you guys are really going to discourage someone who is willing to contribute to an *unmaintained* package just because he wants to use % instead of # and "end" instead of "endif", "endfor", etc. ?

Right. We need all the help we can get. It is that simple.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]